4 ms·

Very few developers are even aware that version numbers were removed so I don't think it's had any real effect on developer confusion. It's probably made it wor

Very few developers are even aware that version numbers were removed so I don't think it's had any real effect on developer confusion. It's probably made it worse. This article complains about WebWorkers which was proposed in 2009 but with the way standards evolve it's hard to know what capabilities it has. Meanwhile Firefox has a solid implementation of CSS calc() but not WebWorkers (which I believe they came up with).

daleharvey 14y ago
In my experience it has helped reduce confusion, I dont see how it could possibly make it worse, unless you count the confusion as developers begin to realise how the web evolves as 'worse', I dont. As said, browser vendors are have no governing body that force them to implement exact specifications at exact times, I dont see how putting a version number on html and pretending that they do is anything but confusing.
- yuhong 14y ago
  Yea, I am thinking "HTML5" even as a buzzword is a misnomer: http://news.ycombinator.com/item?id=4238188 http://news.ycombinator.com/item?id=4238188