|
|
|
|
|
|
by stctw
2520 days ago
|
|
|
That's an interesting thought. It's almost like Chrome and Firefox have been in a "browser cold war" for years now, trying to outdo each other's version numbers, trying to entice users with greener grass rather than the stronger "attacks" of the IE-Firefox "browser wars" of the past, and one side trying to imitate the other. Chrome realized that if it jumped ahead in version number, it could gain a huge PR advantage, and then Firefox was forced to follow that pattern or appear outdated. Users may have gained some rapid iteration, but in the long term, I think we lost the ability to understand how the browsers are changing (of course, some of that is a matter of the inherent complexity explosion in the Web). And once you change to the constantly-incremented version numbering scheme, how can you ever go back to something more meaningful? Who's would blink first? Happily, Pale Moon, for example, retains more modest version numbers. I hope their developers continue doing well. Imagine if it (or a similar project) were the next Phoenix, the way Firefox rose from Netscape's ashes. |
|
|
Personal anecdote, but of all the non-technical people I know (which I define as those who may barely know what a browser is, and only use the computer for browsing a tiny fraction of the Internet), none of them like the constant change, especially when it breaks their workflow, and those who do pay attention to version numbers think the rapid "version explosion" (to quote one) is completely silly. Like a lot of other things in life, they just put up with it because they're powerless.
I really wonder who the browser makers are targeting with the "move fast and break things constantly" attitude, because it's definitely neither the technical nor non-technical users I know.