Since it’s possible to use HTML 5 markup on IE6 (with Javascript: http://html5doctor.com/how-to-get-html5-working-in-ie-and-firefox-2/) is it time to start using it, or is it just too early? I mean, it’s very backwards compatible as it is.
I’m comfortable with XHTML 1 .0 Strict right now, but I wouldn’t mind making the switch if it’s becoming widely acceptable.
I understand that forcing IE users to have working Javascript is kind of a boon, but shouldn’t we be helping users along towards a switch to better, more web-friendly browsers anyways?
For those whom are confused as to what HTML 5 is and what it means for the future of web design, check out the Wikipedia page on the matter. 
Anyways, what are your thoughts?
- Grew a moustache for the Envato Movember competition
- Community Moderator
- Contributed a Blog Post
- Author was Featured
- Item was Featured
- Won a Competition
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Has been a member for 4-5 years
HTML5 ++ !
- Has been a member for 4-5 years
- Item was Featured
- Author was Featured
- Bought between 100 and 499 items
- Referred between 200 and 499 users
- Exclusive Author
- Microlancer Beta Tester
- Author had a Free File of the Month
I think we all have to wait a little bit more.. Javascrip solution for IE6 is not perfect, and it will take some time to get rid of IE6 .. But we’re on the good way 
not yet (unfortunately).
I think once IE6 is gone, we can slowly start using it.
IE6 still comprises of 17% of the market share, which is quite baffling.
HTML5 will be ready and expected to be completely supported in about 2022. People, especially those not working in the field will need to get used to the idea that something else besides the current standards exist.
Plus, try switching doctypes to a fairly complex theme, let’s say a wordpress one, put a HTML5 doctype and try to validate it. You’ll notice that the W3C validator recognizes it’s HTML5 but you will practically have to dump more than half of your current knowledge of xhtml and re-write most of your code in compliance with the new standard.
To me at least, it’s too much of a hassle at the moment and it’s way too soon. Don’t listen to SmashingMagazine or other websites that are very enthusiastic about it and have already started publishing tutorials on HTML5 …they just need stuff to write about.
- Interviewed on the Envato Notes blog
- Microlancer Beta Tester
- Most Wanted Bounty Winner
- Power Elite Author: Sold between 1 000 000 - 1 999 999 dollars
- Author was Featured
- Bought between 100 and 499 items
- Referred between 500 and 999 users
- Won a Competition
HTML5 will be ready and expected to be completely supported in about 2022.
You do understand that we’ll all be operating flying cars and coding in Martian by then right? I honestly don’t know why setting an adoption date that far off is even considered realistic – this would have been like someone in 1880 announcing that the horse-drawn-carriage harnesses were going to be upgraded in 1950. Sure, it’s a great step and hopefully adoption will happen quicker, but technology moves so fast nowadays that it might just become irrelevant.
- United States
- Sold between 250 000 and 1 000 000 dollars
- Has been a member for 5-6 years
- Referred between 100 and 199 users
- Bought between 100 and 499 items
- Author was Featured
- Microlancer Beta Tester
- Exclusive Author
@octofine and @epicera – I couldn’t agree more with both your comments – euphoria seems to be running wild on web blogs about HTML 5 when it’s just simply the wrong move – right now – as we all know we are still struggling to kill of ie6 why start creating stuff that will require even more css specific sheets / workarounds and hacks just to give a small amount of viewers so fancy stuff – just not worth it yet.
And the horse drawn carriage thing was funny dude! 
