Trye, but unfortunately no one can match Chrome teams ability to rapidly ratchet version numbers.
Chrome is is in a weird spot where they "had to" rapidly catch up to MS, but now it is awkward to shoot ahead to version 20 or 30. Presumably his is why they started downplaying version numbers once they caught up.
I wonder if Google is now committed to never break the Eextensions API now. To their credit, Android has done a great job with API compatibility over versions, not breaking old apps. Maybe Chrome can too, and dropping version numbers has raised the bar for software quality, just like forcing auto-upgrades has.
Emacs has followed a similar idea, essentially they just dropped the 1. (or was it 0. - can't remember!), so emacs 23 is really v1.23. Chrome is similar – why use endless non integers for main builds?
I wonder if Google is now committed to never break the Eextensions API now. To their credit, Android has done a great job with API compatibility over versions, not breaking old apps. Maybe Chrome can too, and dropping version numbers has raised the bar for software quality, just like forcing auto-upgrades has.
The whole thing is a bit silly.
This post composed in emacs 23. (Not really)