3 ms·

The problem with Mozilla is that they make the actual number an important part of their communication. With Chrome on the other hand, you rarely hear about vers

The problem with Mozilla is that they make the actual number an important part of their communication. With Chrome on the other hand, you rarely hear about version numbers - you just know they exist and that you don't need to care.

jlongster 15y ago
Not anymore. Mozilla is dropping the version number everywhere, except where it matters. Notice how in the blog posts that there's no version numbers mentioned, anywhere: http://blog.mozilla.com/futurereleases/2011/07/07/firefoxaurora7/ http://blog.mozilla.com/futurereleases/2011/07/07/firefoxaur... http://blog.mozilla.com/futurereleases/2011/05/27/firefoxaurora/ http://blog.mozilla.com/futurereleases/2011/05/27/firefoxaur...
- mhitza 15y ago
  And it matters to extension makers. And those need constant repackaging especially for addons that are no more under active development.
  - bryanlarsen 15y ago
    That's no longer true. http://www.pcmag.com/article2/0,2817,2387399,00.asp http://www.pcmag.com/article2/0,2817,2387399,00.asp
- glenstein 15y ago
  I think this bolsters the criticism. Making a big deal about Firefox 3 did more to spread awareness of the browser than perhaps any other thing Mozilla has done. Version numbers used to be this well-articulated conceptual unit that got people to care about your browser. Now, there's more count-downs to the big release date. No more Guinness World Records for downloads in a day. There is a gimmickiness about it, but I don't have a problem with that given how hard it already is to get laypeople to care about these things.