This "Mozilla is distracted" narrative is a category 5 hurricane of unsubstantiated vibes from people who have no idea what they're talking about.
Some quick hits just from reading recent release announcements from December '25 through April 26:
- Hardware acceleration for faster performance with PDFs
- Expanded WebGPU support
- Faster page loading with compression dictionaries
- Deeper hardware integration for faster video playback on AMD hardware
- Better GPU stability and performance on MacOS
- Faster local translation
And I'm only picking out bits and pieces. "Web platform" improvements are so abundant that reproducing them from any single release would be a massive wall of text, but for a few examples just from one recent release:
>Service worker support for WebGPU has been added, making it available in all worker contexts. Service workers allow WebGPU to run in the background, which is particularly useful for extensions and other pages that can meaningfully share resources across multiple tabs and time periods.
>Firefox now supports the Iterator.zip() and Iterator.zipKeyed() methods from the joint iteration proposal. This allows zipping together underlying iterators into an iterator over values grouped by position, similar to zip in many other languages.
>Firefox now supports the Trusted Types API, which is primarily aimed at preventing cross-site scripting attacks.
>Firefox now supports the Sanitizer API, which provides new methods for HTML manipulation. The element.setHTML() method enables developers to insert HTML content similarly to element.innerHTML, but without the security vulnerabilities such as cross-site scripting (XSS). A complementary method, document.parseHTML(), is also available for parsing HTML safely.
And on and on it goes with APIs, CSS and so on, and that's every release, and that's still not covering feature requests and cosmetic updates, or the constant security updates.
Guys, this is millions of lines of code and thousands of patches every quarter. While you were reading about AI features or poorly worded terms of service, they studied the blade..er.. they worked on real performance improvements. It should be a scandal that anyone in the comment section gets away with claiming they're not working on anything.
Firefox is still very much a technically excellent browser. My plea is simply to stop taking poison pills from the very companies they should be fighting against in standards body discussions. I'd argue Firefox is "behind" in both _marketshare_ and _features_ largely _because_ said features are steamrolled through community governance bodies by the likes of Google, etc. Mozilla is at the table for these discussions but their hands are tied.
Mozilla's continued existence in recent history has relied on money from their primary competitor to stay in operation. Some have argued that doing seemingly unrelated projects like the one announced today is an effort to buy their freedom as it were. I'm arguing that's a distraction and that something closer to Linux or wiki foundation model would allow them to concentrate their efforts where it makes the most sense, as their current governance model is inherently based on a conflict of interest.
Opera was also a technically excellent browser, and we've seen that that alone is not enough to justify its existence in the long term.
Some quick hits just from reading recent release announcements from December '25 through April 26:
- Hardware acceleration for faster performance with PDFs - Expanded WebGPU support - Faster page loading with compression dictionaries - Deeper hardware integration for faster video playback on AMD hardware - Better GPU stability and performance on MacOS - Faster local translation
And I'm only picking out bits and pieces. "Web platform" improvements are so abundant that reproducing them from any single release would be a massive wall of text, but for a few examples just from one recent release:
>Service worker support for WebGPU has been added, making it available in all worker contexts. Service workers allow WebGPU to run in the background, which is particularly useful for extensions and other pages that can meaningfully share resources across multiple tabs and time periods.
>Firefox now supports the Iterator.zip() and Iterator.zipKeyed() methods from the joint iteration proposal. This allows zipping together underlying iterators into an iterator over values grouped by position, similar to zip in many other languages.
>Firefox now supports the Trusted Types API, which is primarily aimed at preventing cross-site scripting attacks.
>Firefox now supports the Sanitizer API, which provides new methods for HTML manipulation. The element.setHTML() method enables developers to insert HTML content similarly to element.innerHTML, but without the security vulnerabilities such as cross-site scripting (XSS). A complementary method, document.parseHTML(), is also available for parsing HTML safely.
And on and on it goes with APIs, CSS and so on, and that's every release, and that's still not covering feature requests and cosmetic updates, or the constant security updates.
Guys, this is millions of lines of code and thousands of patches every quarter. While you were reading about AI features or poorly worded terms of service, they studied the blade..er.. they worked on real performance improvements. It should be a scandal that anyone in the comment section gets away with claiming they're not working on anything.