It has been a few weeks since the W3C announced that the XHTML 2 working group charter was not going to be renewed at the end of the year. With that announcement, it became clear – HTML 5 is the future. Quite a bit of noise followed. Most of it stemmed from existing confusion in the web community around the differences between HTML and XHTML. Now that the dust has mostly settled, I thought I’d stir it up a bit with some quick thoughts on doctypes and complaining versus doing.
Where I come from
The majority of those using the XHTML doctype (myself included) were using it for the stricter syntax. In fact, the XHTML syntax was simply a re-purposing of the HTML syntax with some tighter guidelines. Does it bother me that I was sending XHTML out as text/html? Sure. Do I think it is a perfectly written spec, complete with every feature and semantic consideration I desire? Not really. I didn’t care though. It works and it works well.
In my opinion, the beauty of XHTML Strict was that, regardless of the arguable flaws, it provided the best learning environment. It was not inherently better or worse than the HTML doctype. Rather, for those of us that learned through trial and error; it was a faster way to find our mistakes as we trained to become perfect, code-writing machines.
However, for all intents and purposes, which doctype you used never really mattered. What did matter was that you rolled on something that enabled you in pushing the web forward.
Complaining
Quit it. You shouldn’t be that bent out of shape about HTML 5. I’ve heard complaints about backwards compatibility, code "sloppiness", continuing to support certain elements, extensibility and more. These are well-founded concerns. The problem is, they are rarely discussed in the appropriate context.
Take a step back
First of all, most of those concerns can be applied to HTML 4.01 and XHTML 1.1. Second, the folks that are actually working on the spec can’t possibly get everything right for every single one of us. Additionally, W3C specs are, and always have been, guidelines. You can certainly follow them like rules, but they’re not. If the HTML 5 spec bothers you that much, don’t follow it. There is absolutely nothing wrong with continuing to use XHTML syntax or even an older doctype if you really want to. Complaining doesn’t make issues go away.
Is everyone entitled to an opinion? Absolutely. Is everyone entitled to a spec that is customized to meet their exact needs? Absolutely not.
Keep things in perspective.
Regardless of which spec you prefer, I’d argue that all of us share the same intentions. We all want to make designing for, working on and using the web better. It is completely understandable to be disappointed about any number of things in the HTML 5 spec. If you really want to put your complaints to good use though, here’s how.
Doing
Accept it. HTML 5 is the new hotness whether you like it or not. Start learning about it. Ironically, if you were an XHTML fan, I think this is even more important. The earlier you do, the earlier you’ll begin to understand where the real limitations are for you personally. As with any spec, the greatest benefit in learning them inside and out comes from understanding when it makes sense to stray from them.
If you want to take part in the future of the web, it is your responsibility to contribute positively to it. Complaints are always better when put to use in a positive fashion.
Start using HTML5 (and CSS3)
Use it where appropriate for your own personal projects. Form your own opinions. Discover interesting ways to apply the new features in HTML 5 that you like. At the same time, document unique ways that you’ve worked around those that you dislike. Find and file browser bugs affecting experimental features.
Contribute
Once you’ve juiced up your HTML 5 knowledge, use it to help make HTML 5 better (or more like XHTML 2 if you feel so inclined). If you’re up to it, submit ideas, challenges or code examples to the HTML 5 working group. Talk, blog or speak about what you learned. Build amazing web apps that utilize the new tricks in your toolbox.
Don’t try to hold the web back by complaining. Push things forward by doing.
Helpful Resources
Below is a list of links that I found very helpful in staying up to speed with HTML 5. Enjoy!
Customizable workspaces for online collaboration
The simplest way to send, receive and track large file transfers
Customizable workspaces for online collaboration
The simplest way to send, receive and track large file transfers