The Future: HTML or XHTML
Lachlan Hunt takes a non-religious look forward in The Future: HTML or XHTML. The difference from all the other HTML vs. XHTML articles I have seen is that Lachy states that HTML is (next to) dead, killed by sloppy coding and non-conforming parsers.
- Previous post: Introduction to Web Accessibility
- Next post: EPiServer och tillgänglighet
Subscribe / follow
Sponsors
Authentic Jobs
- Frontend Developer at Momentum Design Lab (San Francisco, CA, US)
- Creative Director at Ai (Alexander Interactive) (New York, NY, Ne, US)
- Mobile Product Designer, Android at Etsy (Brooklyn, NY, Ne, US)
- Senior Visual Designer at Fidelity Investments (Jersey City, NJ, Ne, US)
DreamHost web hosting
Use the promo code 456BEREASTREET3 to save USD 20 when you sign up for DreamHost


Comments
(Why are HTML and XHTML marked up as abbreviations but ‘vs’ not?)
HTML as SGML has always been a pipe dream I guess. I hope HTML5 fixes that.
Because Movable Type and the plugins I use for it aren’t perfect (they don’t automatically recognise every abbreviation that exists), and neither am I (I haven’t entered vs. into the database of abbreviations that should be marked up as such).
The W3C aren’t planning an HTML 5, but might someone else do so? This is a development I hadn’t thought of. I hope someone does. It’d be fun.
People don’t realise it, but HTML 3.2 is actually the future, as IE7 will be more secure whilst reverting its rendering engine back to IE3 due to a source control mishap.
The W3C might adopt HTML5 when it is ready. (I think they will.) Search for WHATWG on Google.
Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.