3 ms·
The previous codebase was left at 68 ESR so the team could work on the new codebase. 68 ESR is now EoL. So now the question is do they try to spend time draggin
by zamadatix 6y ago
The previous codebase was left at 68 ESR so the team could work on the new codebase. 68 ESR is now EoL. So now the question is do they try to spend time dragging the legacy release along into the future and continue to attrition users (FF mobile is already down to ~0.5% browser share) or bet that continuing to focus on the version based on the new codebase will yield better outcomes even if it doesn't have all of the features of the old version.
- tsimionescu 6y ago> bet that continuing to focus on the version based on the new codebase will yield better outcomes even if it doesn't have all of the features of the old version. Ah, executing the famous Netscape strategy, are they? If they were attritioning users already, I shudder to think what will happen with almost no extensions for a few... Weeks? Months? And, if the article is right, also a good number of stability issues.
- Vinnl 6y agoThe few extensions they do have already give them a major leg up over the most commonly used browsers, which offer... 0.
- lawl 6y agoMultiple chromium forks are working at integrating chrome (desktop) extensions (and some already have experimental support). As soon as they do, there's really no point in using firefox anymore. Especially since they seem to give zero fucks about my workflow, I give zero fucks about them.