Mozilla lays off 70

Not sure of Mozilla’s financial or organizational structure but it seems to be part of a larger trend of de-emphasizing QA departments at software shops large and small over the past 10 or so years.

In many ways test automation tooling has become much easier to use, develop, and manage.

But I suspect the larger driving force is that it’s (arguably) a cost center for an org. The burden of ensuring software quality can be shifted to devs and PMs, though usually with mixed results.

For Mozilla, axing quality and security first is a bad look when those are crucial aspects of a privacy-first company value.

If there's anything they need to axe, it's the Gecko team. Just replace it with V8. The whole layout engine too--replace it with Blink. It is inevitable, so might as well get over with it now and save the wasted human effort and $$$.

I tried to use Firefox recently. It leaked 28 GiB of RAM on x86_64 GNU/Linux with no extensions except uBlock Origin. Happened a few times over the month whenever I visited JS-heavy websites. Never had that happen with Chromium, which runs through megs of JS like butter.

Wouldn't it be nice if an experienced browser dev team maintained a privacy-oriented libre version of Chrome (without manifest v3, sync, and all that trash). Or should they keep doing what they've doing and make the best pro-privacy browser that no one ever uses except indirectly through Tor Browser.

> I tried to use Firefox recently. It leaked 28 GiB of RAM on x86_64 GNU/Linux with no extensions except uBlock Origin. Happened a few times over the month whenever I visited JS-heavy websites.

Of course this is not the experience of the vast majority of Firefox users, so it's pointless to suggest that this means something about Firefox's overall quality. You can easily find people making the same sorts of complaints about Chrome.

Considering he was on Linux, btw, that was probably not a Mozilla build.

Sadly, one of the drawbacks of opensource is that people can take your code and butcher it, and users will blame you.

Firefox gigantic leaks happen to me on Windows too. Depending on the mood, it ends with a crash or with Windows warning me that it will kill some processes if that keeps going on.

Happens on mac, too.

Some mornings I'm beachballing for my whole first coffee. Eventually I just wind up power cycling the mac if I can't open a shell prompt with which to `pkill -9 plugin-container`....