I’m a software engineer, and when I build web apps, Firefox now stands in the way of me being able to use new standard features (without polyfills). Meaning, if I want to support the 2-5% of users that may use Firefox, I have to explicitly go out of my way to either make my site less efficient for everyone, or build a special version just for Firefox because it’s so behind, like we used to with IE, making Firefox the new IE (except nobody is really using it). And of course, you can only polyfill so much. Some things are utterly impossible, such as the various PWA features that Mozilla refuses to support, or many new CSS features coming out.
This is sad, of course, as I had used Firefox since it was Phoenix circa 2002, and I kept using it until they decided to nuke all the extensions that kept me using it. They nuked a superior API for extensions, replaced it with Chromium’s extension system, and then only implemented 80% of it, so you couldn’t even use all the Chromium extensions you wanted, making it nearly useless. Less power, less customization, and behind Chromium in every single way. They’ve pivoted to pretending to care about privacy, but trusting another corporation with your privacy is flawed logic. They’ve already started including various ads in Firefox and have installed marketing extensions without consent. Do they really care about your privacy or experience? They care about money, and as their profits get squeezed, they’ll become more desperate and abusive like:
Yeah, I’m also a web developer and this person is completely up their own ass. We’ve all struggled with browsers that lag behind standards (internet explorer) or implement them in weird ways (safari). But Mozilla has never even come close to being a problem like the others.
Also I doubt they are using the newest of new web standards that would actually need to be poly filled and even then with modern JS build tooling poly filling isn’t difficult or abnormal. Oh, the bundle for your crappy SPA might be a few kb bigger but that isn’t gonna make a difference.
I’m a software engineer, and when I build web apps, Firefox now stands in the way of me being able to use new standard features (without polyfills). Meaning, if I want to support the 2-5% of users that may use Firefox, I have to explicitly go out of my way to either make my site less efficient for everyone, or build a special version just for Firefox because it’s so behind, like we used to with IE, making Firefox the new IE (except nobody is really using it). And of course, you can only polyfill so much. Some things are utterly impossible, such as the various PWA features that Mozilla refuses to support, or many new CSS features coming out.
This is sad, of course, as I had used Firefox since it was Phoenix circa 2002, and I kept using it until they decided to nuke all the extensions that kept me using it. They nuked a superior API for extensions, replaced it with Chromium’s extension system, and then only implemented 80% of it, so you couldn’t even use all the Chromium extensions you wanted, making it nearly useless. Less power, less customization, and behind Chromium in every single way. They’ve pivoted to pretending to care about privacy, but trusting another corporation with your privacy is flawed logic. They’ve already started including various ads in Firefox and have installed marketing extensions without consent. Do they really care about your privacy or experience? They care about money, and as their profits get squeezed, they’ll become more desperate and abusive like:
https://www.bleepingcomputer.com/news/security/mozilla-stops-firefox-fullscreen-vpn-ads-after-user-outrage/
Of course your job would be even easier if there was only one engine left. Comparing it to what we had in the IE era though is completely bonkers.
[This comment has been deleted by an automated system]
Yeah, I’m also a web developer and this person is completely up their own ass. We’ve all struggled with browsers that lag behind standards (internet explorer) or implement them in weird ways (safari). But Mozilla has never even come close to being a problem like the others.
Also I doubt they are using the newest of new web standards that would actually need to be poly filled and even then with modern JS build tooling poly filling isn’t difficult or abnormal. Oh, the bundle for your crappy SPA might be a few kb bigger but that isn’t gonna make a difference.
To name a big one: the CSS :has() pseudo-class.
How is this still not enabled by default?
[This comment has been deleted by an automated system]
Side panel, workspaces, tab-stacking, just to name a few.
[This comment has been deleted by an automated system]
“What major standard features is Firefox missing these days?”
This was your question, nowhere did you say anything about web API’s. You stupid or just forget which comment I was responding to?
Sure FF has extensions that “kinda do the same thing” except they’re shit and bloat the browser beyond what it already is compared to Vivaldi.
[This comment has been deleted by an automated system]