Yeah, the checklist of web technologies is getting longer, but that's only part of the solution. They don't all work together very well. For example, Alex Russell has been opining recently about the way DOM interfaces are awkwardly adapted to JavaScript due to the committee's insistence on targetting IDL. That's why the W3C could never have invented jQuery.
I've been trying to duplicate native scrolling in iOS recently and I'm getting killed by details that the specifications don't cover and WebKit authors don't document. For example, tons of trial and error uncovered the fact that CSS keyframes animations are unusable for elements wider than 1024 pixels, due likely to OpenGL issues on iOS. If the W3C and WebKit had any clue how developers would actually use the stuff they design, they would have made this fact clear by at least providing a way to query the optimal texture size used under the covers.
Over and over you find little examples like this which demonstrate that the web's "leadership" is completely disconnected from reality on the ground.
I've been trying to duplicate native scrolling in iOS recently and I'm getting killed by details that the specifications don't cover and WebKit authors don't document. For example, tons of trial and error uncovered the fact that CSS keyframes animations are unusable for elements wider than 1024 pixels, due likely to OpenGL issues on iOS. If the W3C and WebKit had any clue how developers would actually use the stuff they design, they would have made this fact clear by at least providing a way to query the optimal texture size used under the covers.
Over and over you find little examples like this which demonstrate that the web's "leadership" is completely disconnected from reality on the ground.