Anyone who thinks they know what needs to happen for Firefox to regain market share, needs to consider what would happen if someone forks Firefox and makes that happen.
There’s no way that CSS theming is it. And in general, “not doing something” isn’t going to be it, either.
they need to offer a better alternative to Electron. once that happens, you’ll have Firefox everywhere. People will code their SPAs to run in Firefox first, recommend it to their users, and accelerate the development of better APIs.
oh don’t get me wrong if I had a plan for it I’d be doing it. I’ve always found it really weird given the impact that Electron had in app development, why Firefox never tried to ride that train. I know of one short lived effort to take the engine out of the browser.
Usually the answer is limited resources with unclear payoff, i.e. even with Electron’s success, it’s not clear that there’s room for an alternative in the market, and it’d be a lot of effort to do.
Tauri v2 just got released, it’s very recent and corps move slowly; besides, rewriting a project in a different framework is a major undertaking, it would be a bad idea to rewrite a major project in Tauri, which is still not as widespread. I’m unfortunate enough to have to work with Electron and Tauri greatly improves on everything that is wrong with Electron. I have no doubt that companies will begin adopt it in the following years (or a similar tool, the underlying architecture is solid).
Anyone who thinks they know what needs to happen for Firefox to regain market share, needs to consider what would happen if someone forks Firefox and makes that happen.
There’s no way that CSS theming is it. And in general, “not doing something” isn’t going to be it, either.
they need to offer a better alternative to Electron. once that happens, you’ll have Firefox everywhere. People will code their SPAs to run in Firefox first, recommend it to their users, and accelerate the development of better APIs.
Check out Tauri, a better alternative to Electron. It avoids bundling a browser engine in the binary and relies on the OS browser engine.
Ah, so it should just be better! I wonder why nobody thought of that yet :P
(Sorry, I’m in a sarcastic mood, but you get my point.)
oh don’t get me wrong if I had a plan for it I’d be doing it. I’ve always found it really weird given the impact that Electron had in app development, why Firefox never tried to ride that train. I know of one short lived effort to take the engine out of the browser.
Usually the answer is limited resources with unclear payoff, i.e. even with Electron’s success, it’s not clear that there’s room for an alternative in the market, and it’d be a lot of effort to do.
There is Tauri which is so much better both from UX and DX.
And yet all the big apps are still using Electron.
Tauri v2 just got released, it’s very recent and corps move slowly; besides, rewriting a project in a different framework is a major undertaking, it would be a bad idea to rewrite a major project in Tauri, which is still not as widespread. I’m unfortunate enough to have to work with Electron and Tauri greatly improves on everything that is wrong with Electron. I have no doubt that companies will begin adopt it in the following years (or a similar tool, the underlying architecture is solid).