Chromium and Firefox both consume obscene amounts of memory just to do basic things, more or less equally. However that changes when you're working locally using many applications, compilers, several terminals, code editors, and many documentation tabs open in the browser (can't close all docs I need whilst coding)
I've stress tested the machines I use for work and forced the memory available down to a lower limit to see how these two browsers behave under different conditions. Chromium / Chrome doesn't relinquish RAM as efficiently as Firefox does. Firefox uses inordinate amounts of RAM, but it knows better when to free it, and I'm able to use even limited memory configurations under stress tests with many tabs open. Chromium / Chrome just freezes randomly if you have 8 or 10 tabs open whilst doing equivalent work, sometimes to the point of halting the whole system.
For heavy duty work, Firefox just works better.

@h That might be due to Firefox being written largely in Rust, as precise and efficient memory tracking at compile time was the one of the features it was specifically designed for. 🙂


@vertigo That seems to be the case wirh Firefox Quantum, indeed. Although not all of Firefox has been re-implemented. I believe I read months ago that only the CSS engine was rewritten in Rust **and** shipped. It's quite possible that other parts of Firefox have been re-implemented since then as well.
In parallel there's also the Servo browser (being written from scratxh in Rust) which isn't yet very usable at this time, but I'm hopeful it can deliver even better results if it does away with the resourcehognness of current browsers.

Sign in to participate in the conversation
Sunbeam City 🌻

Sunbeam City is a Libertarian Socialist solarpunk instance. It is ran democratically by a cooperative of like-minded individuals.