HTML5 kills XHTML2

The big news last week, well at least to some, is that XHTML 2.0 bites the dust. The W3C has decided to kill the project off. Well, it’s a bit more like tying it to a tree in the woods and driving off. It seems that they, wisely, considered XHTML2 a waste of time. I couldn’t agree more. What many don’t realise is that XHTML in general had never really made it in any of its incarnations. No point in flogging a dead horse/media type.

It’s funny to see some reactions on Zeldmans site that really show that web standards is often used as a front so one can fit in. I’ve actually heard someone, in a job interview, proclaim, “… as an expert I only use XHTML in all my work. It’s the only way to go…” That was one of the quicker interviews. If you’re wondering about XHTML2 then Henri Sivonen has nice little write up that sheds a little light on the matter.

I’ve said it before and I’ll say it again. HTML vs. xHTML, I don’t fucking care.

I like the xHTML syntax, I always have. It somehow makes my work look a little cleaner. It’s also easier to wrangle non-web developers into getting the front-end to validate a little more. Just a little, because I know they really don’t care. But if they wanted to work with HTML syntax that would be fine with me to. Just be consistent. It’s all just text/html anyway.

The HTML5 movement is interesting because it’s the only current development that has actually made it in to real browsers. The focus on video at the moment is way over the top because most websites don’t deal with video at all. What I find encouraging is that they’ve made the mark-up a little more structural in nature and described how it should behave under different circumstances. The adoption of HTML5 along with CSS3 is making a lot of head way. I really don’t see how Microsoft can abstain from this renewed urgency in browser technology. My gut feeling is that they’re working their little cotton socks off to get next release ready with HTML5 and CSS3 bits in place.

So far not much, if anything, has changed for me. I’ll still be using the current doctypes for a while and from time to time I may sneak the HTML5 doctype into a project here and there.

Next entry: HTML5, the rise of the cloud
Previous entry: Usable fonts