To read all comments associated with this story, please click here.
"Complaining about HTML5 now doesn't make a lot of sense to me. The standard isn't finished"
On the contrary. That is why we can complain about it. Big standards are always slow, complicated, and hard to get agreement. Thus they always lag behind the nimble products that might not be as 'standard' but are designed to get things done.
Ultimately, HTML will face the same problem as Java. HTML (not just HTML, but AJAX...) is trying to become a universal programming API. It stopped being a markup language long ago.
Edited 2011-02-04 14:05 UTC
On the contrary. That is why we can complain about it. Big standards are always slow, complicated, and hard to get agreement. Thus they always lag behind the nimble products that might not be as 'standard' but are designed to get things done.
Ultimately, HTML will face the same problem as Java. HTML (not just HTML, but AJAX...) is trying to become a universal programming API. It stopped being a markup language long ago.
If big standards are slow and complex then maybe it should be broken into smaller projects and allow those components that are non-controversial to move forward whilst spending time addressing the ones that are a little more controversial. Having a large 'umbrella' standard such as HTML5 is all very well and good but keeping in mind the better way of addressing such a complex issue is to take a piece meal approach so that each group can advance forward at its own pace as not to hold up development over all.
I also have an issue with the fact that W3C is chocked to the brim with vendors who aren't even making web browsers or anything related to the internet; sorry, why should an organisation who has no vested interest, other than protecting their monopoly/market dominance in a particular area, hold up the development of a standard by fillabusting any sort of development forward.
Take a look at this list:
http://www.w3.org/Consortium/Member/List
And I'd love someone to explain to me why even half those people are at the discussion table - clingers on, hangers on and oxygen thieves who quite frankly contribute nothing; most of them don't make browsers, development tools or platforms so why the hell are they even there?
The linked article is not complaining about HTML5, itself.
It's complaining that HTML5 is in beta state, but Apple and Microsoft are touting it has the way to go, even though they know it is incomplete, and their own implementations are buggy and incomplete and inconsistent as hell.





Member since:
2006-06-28
Complaining about HTML5 now doesn't make a lot of sense to me. The standard isn't finished, we are speaking about drafts and many browsers don't implement every piece yet, because the developers are afraid that they would have ti implement it multiple times. Websockets or push-technologies in general are a great example.
It doesn't really make a whole lot of sense to complain about stuff like performance of an unfinished (I mean nowhere near) implementation when there isn't even a finished standard for most HTML 5 parts.
I still think it's a good thing to criticize a standard before there is a final version, so it can be changed. That's also why browsers should implement unfinished stuff, even if it is going to change. Feedback of people implementing this stuff is usually very welcome. As long as it isn't about using patented formats.
There is still a competition about the fastest JavaScript implementation and therefor I believe JavaScript or canvas will stay that slow.
Who care about iPads anyway? :p
Not that it is just one way to access the internet and if it is that successful I bet there will be a new version. Else web developers will at some point (when HTML5 is finished) be able to drop it. Like they dropped IE5.