I decided to dive in to HTML5 and CSS3 in my last project and I'm really happy I did so. So much so, in fact, that I won't look back -- at least, not for my own projects.<p>Previously anything that came out of W3C was more akin to something a company that didn't listen to its customers would produce but it seems like they broke that habit with HTML5. There are some technical details that are still up in the air (i.e. video codec -- but I'm not really sure what the status of that is) but one certainly good quality of HTML5 is that you have to be almost stupid to write non-validating markup.<p>Also, there are a lot of little things that they implemented that are really valuable to rich apps. For instance, custom data attributes -- which I wrote about a few months ago (herp derp, self promotion: <a href="http://bradhe.wordpress.com/2010/08/31/custom-data-attributes-are-your-frien/" rel="nofollow">http://bradhe.wordpress.com/2010/08/31/custom-data-attribute...</a>) -- finally fixes the coupling (or decoupling, actually) issue that has been present in HTML + JS apps until now!
There is a bit of bad advice in here. You would want to do<p><pre><code> <ul>
<li>something</li
><li>something else</li
><li>yet another thing</li>
</ul>
</code></pre>
This allows you to use <i>display: inline-block</i>. If you put each <i>li</i> on a separate line there will be a single space between the elements.
Interesting article.<p>I wish he hadn't dropped "Why the $f not?" line. I'm not offended, but it comes off as unprofessional in otherwise well written content.