haha, I think about a decade ago, W3C was actively trying to dissuade
people from using lt;b> and *lt;i>, something about how *lt;strong> and
*lt;em> are better. But I was like "but those words take longer to
write???" I mean, it's the same movement that wants us to put a / in the
*lt;img /> and *lt;br /> tags because they don't have a closing tag, but
honestly I don't care. And since I live in an area with a lot of
professional web developers, they're always like "but the *right way is to
..." and I'm like "well let me see you quickly subdivide this row into
thirds without using tables" and they're like "well if you do a div with a
flexbox and build in flow deprecation then..."
That said, I agree that *lt;blink> and *lt;marquee> should be deprecated
no subject
haha, I think about a decade ago, W3C was actively trying to dissuade people from using lt;b> and *lt;i>, something about how *lt;strong> and *lt;em> are better. But I was like "but those words take longer to write???" I mean, it's the same movement that wants us to put a / in the *lt;img /> and *lt;br /> tags because they don't have a closing tag, but honestly I don't care. And since I live in an area with a lot of professional web developers, they're always like "but the *right way is to ..." and I'm like "well let me see you quickly subdivide this row into thirds without using tables" and they're like "well if you do a div with a flexbox and build in flow deprecation then..."
That said, I agree that *lt;blink> and *lt;marquee> should be deprecated