Is it not? I honestly can't think of anything I'd want it to do more than it already does. I'll be honest, it is difficult to distinguish between browsers these days. But we have holy wars like vim vs emacs, when really the differences are quite small and rather dumb.
The reason I use Firefox is literally three things: 1) I don't want Chrome to have a monopoly, 2) I get ad blocking on my phone, 3) if I'm going to install an ad blocker on my browser, I also want my browser to not be tracking me. I'll be honest, these are the only truly unique features (that I use). Otherwise it is near indistinguishable from Chrome.
I'm happy with FF and while that's still true I don't mind Mozilla branching out. If I wasn't happy, then yeah, there's a priority issue. But honestly, what's so important that's missing? I don't get this holy war. It just seems like war for the sake of war, and no one benefits from that except those on top.
And yes, I have a valid reason to use webworker: I'm making writing an online compiler playground.
More than half the time, the firefox debugger plainly crash when opening my app, and I have to open a new tab and retry.
For some reason I can't put a breakpoint on the statement after an if on the same line.
And these are my issue only on the last hour ! I'm using firefox everyday but yes, there is room for improvement.
I expected them to add Time Travel Debugging: https://www.bleepingcomputer.com/news/software/firefox-is-te...
It was working on mac, then they fired a lot of staff, including the one who were developing it, and now they made their own company out of it: https://www.replay.io/
And to the one who says "you can contribute", yeah no, I tried, the official docs (back then) gave you the non-optimal ste^s (full clone of the repo (multiples hours due to upstream servers being slow), full local compilation).
The worst of it is, the doc tell you to compile firefox, so multiples minutes of wait to test a change, a change made to the devtools, which is entierely written in JS.
Oh and of course, you can't plug a debugger on the devtools, so you are stuck with console.logs.
Edit: minutes after writing this comments, my just tab crashed: https://i.imgur.com/s1y1JsO.png
Eich's back at it again :D.
Give me 4x less battery draw and I'll try Firefox again, I want to use and like Firefox but every time I give it a go power usage remains a massive issue. I get at least 4x less power draw in the same activities on chromium based browsers and safari.
Thats my main use case for Firefox extensions
I still have Firefox on all my devices and seriously hope they focus on engineering instead of playing ideology when their revenue stream is shaky at best. I’d honestly pay for tab continuity and other UX improvements as a feature if they improve their css and js engines. I know that chromium has now become what IE was at one point but if Firefox can’t render properly and provide consistent js performance I find it harder and harder to recommend to non technical users.
This is from someone who evangelized FF in the 2010s and got many friends on board.
Mozilla spent $262M in 2020 [1]. They manage money poorly.
[0] https://www.apache.org/foundation/docs/FY2021AnnualReport.pd...
[1] https://assets.mozilla.net/annualreport/2020/mozilla-fdn-202...
You don’t have to pay $100M in developer salaries to produce great software. Mozilla is not that great despite having lots and lots of employees.
Perhaps rethinking their approach would be useful. But if their revenue goes away, it doesn’t mean Mozilla the browser goes away.
Maybe Mozilla should just be a governance process rather than a software developer. The browser would probably have similar quality.
Who would employ people to work on Firefox if the corp side shuts down eg. because they lose their revenue?
If these were business lines then of course it’s bad to have stinkers or abandoned products. But with Apache products it doesn’t cost them anything (or almost nothing) to keep them around and have amazing products (httpd, spark, lucene, etc) ad well.
I think the issue with Mozilla is that their browser has really floundered despite spending hundreds of millions of dollars on development. That’s the problem they need to fix. It would be curious to see what Google’s spend is on Chromium and Chrome. I’d be surprised if they have 100 developers working on it.
After that go down the org chart and fire everyone not coding for the browser.
Then you can live off donations until the end of time.