Firefox 124.0, See All New Features, Updates and Fixes
www.mozilla.org
    • Ephera ( Ephera@lemmy.ml ) 
      3·
      3 years ago

      Yeah, kind of unfortunate that it didn’t do much at the start and people were asking themselves why it’s there, but from a development perspective, it absolutely makes sense that they wouldn’t implement everything ahead of time, before getting feedback from users…

        • Ephera ( Ephera@lemmy.ml ) 
          2·
          3 years ago

          If you’ve got qualitative feedback about the implementation, like you wanted to use the Shopping sidebar, but the text was much too small on your device, or maybe you found a vulnerability in their ad network implementation, which allows tracking individual users, then the developers absolutely want that feedback.

          If your feedback is “Don’t roll these out!”, you’re still free to give that feedback, but yeah, that’s not useful in the development process.
          You’d need to address that to management and ideally include a really good idea for how else to secure the wages of their employees. “Don’t make any money!” and “Please, fully rely on the money from Google!” are not useful as feedback.

            • Ephera ( Ephera@lemmy.ml ) 
              1·
              3 years ago

              You seemed to be going off on a tangent about their strategic decisions, when I was talking simply about the feature development process.

              I have no interest in discussing their strategic decisions, because flaming about it in some random internet forum isn’t going to change anything anyways.
              If there was a chance that we worked out a more viable strategy, which Mozilla could tangibly realize, that would be different. But presumably, neither of us work in a full-time managerial position at Mozilla, so to assume so, would be absolute madness.

    • ahal ( ahal@lemmy.ca ) 
      5·
      3 years ago

      In the rapid release model there are no updates bigger than the regularly scheduled releases. So each regularly scheduled release needs to bump the biggest version number. Otherwise the biggest number would never change and there would also be fewer ways to distinguish smaller releases.