Please replace the LAMP.

Unfortunately this is another feature-list presentation. I'm not sure which part of it was aiming to convince people that HTLML is ready?

I'm all for HTML5 and use it for my personal projects, however there's nothing out there that would convince a company with many developers working on and maintaining hundreds of projects most of which must be pretty much 100% IE6, 7 and 8 compatible that it's ready for adoption.

I'm working on updating our front-end framework and development guidelines, but there are just way more obstacles to handle than benefits gained from going HTML5. For years I've been (re)preaching not relying on JS for basic and fundamental things, but there's no other way for. Too much overhead that takes time to develop, implement and maintain, which equals money.

I'd like to take the approach of gradual implementation of features, but it creates convoluted and constantly changing guidelines and leaves a trail of inconsistent websites which are difficult and time consuming to maintain.

I'd love to see answers to these problems, or at least someone acknowledging them.

P.S. The link in the first comment is unfortunately not a solution to anything, just another hacky workaround.

Thanks for the feedback Istvan. You're right, this is a very entry-level, feature-list style presentation. The purpose was to introduce a crowd of about 30 fellow Refresh Columbia (refreshcolumbia.org) members to the subject and provide resources for them to learn more and begin experimenting with HTML5 in their daily work. I did not intend for it to be a global resource and certainly did not mean to say that everyone should immediately use all of HTML5 in production.

Now...whether or not HTML5 should be used in production is debatable. It's true that a company that maintains a lot of projects that still require IE6 compatibility wouldn't be a likely fit. If you're updating your front-end framework though, it makes a lot of sense to at least switch doctypes and start using HTML5 class names on all new projects to ease the transition. The company I worked for previously had just such a structure and we started doing this over a year ago. It makes no sense to completely ignore HTML5 for production work until IE8 or even until IE7 disappears. The web is in a constant state of evolution and if you aren't gradually implementing new features, you'll be quickly left behind.

P.S. I agree.

noob.be is a dutch belgium website watching all html5 developments and posting interresting links and offcourse Jason beaird is on the html5 watch list, but what's up with the [link rel="stylesheet" file="style.css"] (using brackets instead of gt and lt) that does not work...or was that an illustration?

Thanx for the slides!
I used the brackets for illustration because the comment box doesn't accept my gt lt chars.. ;) but I mean the file attribute of the link tag.. is that correct?

Er, no...that's not correct. I didn't even see that when I went back and looked at the slide again. It should be href. Good catch and sorry for the confusion.

I should have read on, cause I did the same thing, I followed the file attribute and no success on the link to css.

Thanks for the presentation. Keep it up.