For a definition of "efficient" that isn't shared by anyone else. This isn't a new rationale either, but a well known trade-off involved with JIT compilation and garbage collection. It's the reason Chrome "hogs" memory and Firefox is perceived as slow: they make different resource usage tradeoffs.

It will be interesting to see if the current memory crunch will impact this calculus going forward.

▲

himata4113 2 days ago | parent [-]

Firefox uses more memory than chrome in all my tests when I was using it for VNC (x11).

▲

TexanFeller 2 days ago | parent [-]

FF seems to use less RAM than Chrome for my 100+ open tabs these days. It’s just as fast for 99% of sites and surprisingly even compatibility is often better. Half the time when my wife encounters a broken webapp in Chrome it works fine when I have her try in FF.

	▲	himata4113 2 days ago \| parent [-]
		that seems kind of irrelevant since that's just based on how aggressive backgrounding is no?