3 ms·
> There's the "let's throw out semantic versioning since Chrome already did it" Firefox never followed semantic versioning. Versions 2.0, 3.0, 3.5, 3.6, and 4.
by jcranmer 11y ago
> There's the "let's throw out semantic versioning since Chrome already did it"
Firefox never followed semantic versioning. Versions 2.0, 3.0, 3.5, 3.6, and 4.0 all had equally major changes to them. It's worse if you look at the internal version numbers: 1.8, 1.9, 1.9.1, 1.9.2, 4.0. The change to the rapid-release model was driven more by the pain of the protracted Firefox 4 release than by trying to ape Chrome.
> There's the UI rework which sacrificed information density and usability for what I evaluate as a weak attempt to look more like Chrome.
Actually, Firefox started developing the design before Chrome did. They just took far, far, far longer.
- Karunamon 11y agoFair enough on the versioning thing - but as far as the UI, Chrome's main interface has remained almost identical to its initial release seven years ago. Firefox was really working on something similar for that long?
- JonathonW 11y agoAs far as I can tell, the Australis work dates back roughly to 2012 (that's when their wiki meeting notes start, and when the Australis tracking bug in Bugzilla was opened). You may be mixing Australis up with the theme work done for Firefox 4.0 (which moved tabs to the top by default and added the orange Firefox menu button). The early work on that would've been contemporaneous with the earliest public versions of Chrome (2/3/4)-- the design that would become Firefox 4 started being shown off in public around the fall of 2009.