I would argue that Electron webapps shouldn’t really count towards the browser marketshare. If would be nice to have a Firefox version, but it doesn’t matter precisely because the end user is not choosing the browser - the company pushing the product is. And let’s be honest: nerdy HN users aside, Joe Schmoe has no clue Teams is a web app running in an emasculated browser at all.
> I would argue that Electron webapps shouldn’t really count towards the browser marketshare.
Perhaps not, but if you're writing your desktop app in Electron, you'll be benchmarking your performance optimizations against the Chrome engine. If that same code is used for your web app, you're optimizing your website for Chrome.
Mozilla can pour resources into making Firefox more performance, but the real-world ecosystem will change behavior to improve Chrome's performance on their webapp with little concern as to whether it hurts Firefox's performance.
(I assume people use largely the same code between Electron and their webapps, and that optimizations for Electron translate reasonably well to optimizations for Chrome.)
every time someone uses electron they buy into the chrome ecosystem -- when they run into problems they write mailing list posts or stack overflow questions that other people can read to help them when they have the same problem, and if they actually want to contribute bugfixes or features upstream they go into chrome not firefox. also if they have a webapp version the webapp version that's running in chrome works exactly the same as the same code running in electron without really having to do any separate testing so which browser are they going to push to be used internally?
