Earlier quoted context omitted.
i wish firefox had more granularity with its tab unloading feature. one method is restarting browser. but by default it’ll unload tabs if you’re low on memory. you can force em in about:unloads (hint- about:about if you ever forget) i wrote a simple firefox extension that unloads em all with a button click, but it’s no different than restarting ff or spamming clicks in :unloads
We already know the solution. We run the browser in Wasm inside the browser. That way it only has one tab open and that tab is doing 99% of its work inside of a wasm env. I thought firefox would ship new versions of firefox inside of firefox at some point. I guess that point is still in the future. This of course is how electron should work as well. A canvas only frame that loads whatever rendering system you want, w…
How many levels of abstraction do we need to run software reliably? The fact that browsers have effectively become operating systems should be worrying enough.
No wonder we have all these fantasy projects that take us back to when our computing environments were actually pleasant to use. I would partly blame the invasive tracking and needless complexity of modern OSs for that, but the ever growing software layers around hardware makes no sense at all. We should question any such design decision, and strive to simplify this ball of complexity instead.