7 ms·

Celebrating Firefox: How we got to 100

Vladimof 4y ago
"How we got to 100?" Easy answer... they stopped going from 1.01 to 1.02... and instead went from v1.02 to v6.6
forgotmypw17 4y ago
My application is at version 9000+, thanks to counting each git commit as a version... and it still supports http, unlike Firefox 100.
- sam_goody 4y ago
  That's pretty impressive, as most projects never get to 9k+ commits. You should celebrate 10000 when you get there, since that would probably be appropriate considering your preferred scheme. Care to share what your app is?
  - forgotmypw17 4y ago
    Sure, it's a hybrid static-dynamic site generator with a focus on accessibility, compatibility, and transparency. I've been working on it for about 5 years, though I recently did a purge of the git history during a rename. The link is in my profile, and the repo can be found by searching that string on google (with quotes) plus github :)
terminal_d 4y ago
If firefox wants to differentiate itself from Chrome (and I'm not fully sure it does want to anymore...) it needs to stop mirroring it and focusing instead on the people that do use it and not on somehow capitalizing on ever-greater marketshare.
- hulitu 4y ago
  Firefox does not want this. I use it only for things which require IE6 (Chrome, Firefox or Safari). The first thing it does when it starts, it connects to some cloud. So much for user privacy.
hoseja 4y ago
... by aping Chrome's versioning scheme, but respectfully staying a couple numbers behind their master. Also, >For clutter-free history, instead of an endless sea of URLs leaving you feeling overwhelmed, we’ve organized it for you in an intuitive way. Nice way to say, "we dumbed it down and removed useful features."
- theandrewbailey 4y ago
  > but respectfully staying a couple numbers behind their master. Firefox has been steadily closing the version number gap over the past few years. Today, there's Firefox 100 next to Chrome 101. Firefox will probably lap them sometime this year. Firefox 105 planned release on August 23rd, but Chromium 105 on August 30th. https://chromiumdash.appspot.com/schedule https://chromiumdash.appspot.com/schedule https://wiki.mozilla.org/Release_Management/Calendar https://wiki.mozilla.org/Release_Management/Calendar
  - zamadatix 4y ago
    > Firefox 105 planned release on August 23rd I think you're reading the beta version number to the left instead of the release version number to the right as that date is for the release of 104. Both are on a 4 week release cycle now so it's up to any delays to change the gap.
    - theandrewbailey 4y ago
      Oh, you're right! I guess that dream has been postponed indefinitely.
- bwat48 4y ago
  The release cycle is absolutely nothing to do with chasing version numbers. It's about being able to ship new features when they are ready, instead of waiting for a 'major' new version. This release cycle makes the most sense for 'evergreen' software like a web browser. There's a reason why every major browser has adopted it. The only version that matters for a web browser is the 'latest' version.
svnpenn 4y ago
FYI, Firefox Android has basically killed add-ons, similar to Chrome. You can only install custom addons if you register with Mozilla: https://github.com/mozilla-mobile/fenix/issues/20647 https://github.com/mozilla-mobile/fenix/issues/20647

"How we got to 100?" Easy answer... they stopped going from 1.01 to 1.02... and instead went from v1.02 to v6.6

My application is at version 9000+, thanks to counting each git commit as a version... and it still supports http, unlike Firefox 100.

sam_goody 4y ago
That's pretty impressive, as most projects never get to 9k+ commits. You should celebrate 10000 when you get there, since that would probably be appropriate considering your preferred scheme. Care to share what your app is?
- forgotmypw17 4y ago
  Sure, it's a hybrid static-dynamic site generator with a focus on accessibility, compatibility, and transparency. I've been working on it for about 5 years, though I recently did a purge of the git history during a rename. The link is in my profile, and the repo can be found by searching that string on google (with quotes) plus github :)

terminal_d 4y ago

If firefox wants to differentiate itself from Chrome (and I'm not fully sure it does want to anymore...) it needs to stop mirroring it and focusing instead on the people that do use it and not on somehow capitalizing on ever-greater marketshare.

hulitu 4y ago
Firefox does not want this. I use it only for things which require IE6 (Chrome, Firefox or Safari). The first thing it does when it starts, it connects to some cloud. So much for user privacy.

hoseja 4y ago

... by aping Chrome's versioning scheme, but respectfully staying a couple numbers behind their master. Also, >For clutter-free history, instead of an endless sea of URLs leaving you feeling overwhelmed, we’ve organized it for you in an intuitive way. Nice way to say, "we dumbed it down and removed useful features."

theandrewbailey 4y ago
> but respectfully staying a couple numbers behind their master. Firefox has been steadily closing the version number gap over the past few years. Today, there's Firefox 100 next to Chrome 101. Firefox will probably lap them sometime this year. Firefox 105 planned release on August 23rd, but Chromium 105 on August 30th. https://chromiumdash.appspot.com/schedule https://chromiumdash.appspot.com/schedule https://wiki.mozilla.org/Release_Management/Calendar https://wiki.mozilla.org/Release_Management/Calendar
- zamadatix 4y ago
  > Firefox 105 planned release on August 23rd I think you're reading the beta version number to the left instead of the release version number to the right as that date is for the release of 104. Both are on a 4 week release cycle now so it's up to any delays to change the gap.
  - theandrewbailey 4y ago
    Oh, you're right! I guess that dream has been postponed indefinitely.
bwat48 4y ago
The release cycle is absolutely nothing to do with chasing version numbers. It's about being able to ship new features when they are ready, instead of waiting for a 'major' new version. This release cycle makes the most sense for 'evergreen' software like a web browser. There's a reason why every major browser has adopted it. The only version that matters for a web browser is the 'latest' version.

svnpenn 4y ago

FYI, Firefox Android has basically killed add-ons, similar to Chrome. You can only install custom addons if you register with Mozilla: https://github.com/mozilla-mobile/fenix/issues/20647 https://github.com/mozilla-mobile/fenix/issues/20647