3 ms·
This is the same strategy that wrecked Eclipse and Firefox. Every 6 months is just too quick for most people to feel comfortable, and will cause fragmentation
by g051051 9y ago
This is the same strategy that wrecked Eclipse and Firefox. Every 6 months is just too quick for most people to feel comfortable, and will cause fragmentation as the 3rd party ecosystem updates things at different rates.
- oblio 9y agoCounter example: Chrome.
- g051051 9y agoChrome makes continuous small changes. It doesn't make big breaking changes every 6 months, whether the community and ecosystem are ready or not.
- oblio 9y agoI don't get why Firefox gets flak, then. They broke compatibility with v57 exactly for that: to make continuous small changes. The previous situation was untenable since there was no API for extensions, the extensions could just go through Firefox internals and change at-will whatever they wanted. The whole point of WebExtensions is that they won't need to break compatibility after this huge leap.
- g051051 9y agoFireFox constantly broke all my extensions with just about every minor update. It was maddening. After being a die-hard FireFox/Netscape/Mozilla user since the 90's, I finally gave up a few years back and switched to Chrome. I can't recall a single time since then when my browser or extensions stopped working because of any update, not just a minor one.
- oblio 9y agoYou should maybe check things out again, cause that’s why they made this huge change in Firefox 57.