Re:The Pain of HTML5
by MatthewPhillips on Monday July 16, 2012 @12:28PM
(#4251334)
> Version numbers do little to prioritize engineering work.
Then the problem is bigger, because in the larger software world version numbers are used and matter.
Sorry if you took my comment as the implication that version numbers don't matter; they certainly do. But the relationship between specifications and browsers is complex.. My point is only that putting version numbers (instead of timestamped commits) on a spec doesn't assist browser makers.
Specification test suites are really our greatest hope at early cross-browser compatibility and right now they're not in a great state. See also testthewebforward.org which aims to assist this (and movethewebforward.org which birthed it)
The demands of application developers are much of what drives feature prioritization inside browser developers. Scores and benchmarks certainly contribute, but it'd temper that a bit.. see the recent Maxthon kerfuffle on how browser's have their feet held to the fire on their scores: http://www.favbrowser.com/maxthon-scams-its-score-in-html5te...