4 ms·
I'm guessing, but if I had to bet, @namespace is almost certainly a holdover from those bad ol' pre-HTML5 days when the W3C was still pushing XHTML. I'll be ho
by CarelessExpert 5y ago
I'm guessing, but if I had to bet, @namespace is almost certainly a holdover from those bad ol' pre-HTML5 days when the W3C was still pushing XHTML.
I'll be honest, I miss the consistency and regularity of XHTML. And being able to hook into the XML ecosystem is really attractive. But, at this point, it seems likely to remain in the dustbin of technology history...
- toxik 5y agoXHTML was a neat idea, replaced by something much less elegant.
- sigg3 5y agoDHTML and ASP?
- com2kid 5y agoMy main irritation with XHTML was that any tiny mistake in it rendered the document not visible at all. Oh and how picky the <head> tag had to be specified. It didn't help that this was all done back in the days when HTML pages were still often hand written. Now days with HTML being largely framework generated, XHTML would be awesome!
- CarelessExpert 5y agoOh yeah, HTML had ergonomics that made it easier to use by humans and a lot harder to use by computers. XHTML is basically the opposite. As a former coder, I support that tradeoff. As a user... well, there's many reasons XHTML failed, and that's definitely one of 'em!
- pjmlp 5y agoIt mostly failed because browser vendors in general didn't care enough, and then Mozilla pushed HTML 5.
- blooalien 5y agoI could actually totally see that @namespace thing bein' useful if you're embedding SVG directly into your HTML (which is entirely possible, and even useful sometimes).