What can be done about modern web browisng using so much fucking ram?

What can be done about modern web browisng using so much fucking ram?
Can websites be compressed like on the browser like a zip file or something?
Somebody think of something.

Attached: download.jpeg-54.jpg (300x168, 9.2K)

Other urls found in this thread:

firefox-source-docs.mozilla.org/dom/ipc/process_model.html
twitter.com/AnonBabble

>Compress
>In ram
>While being used

Rejecting React. It's that simple.

Simpler websites

>What can be done about modern web browisng using so much fucking ram?
reduce javascript use
>Can websites be compressed like on the browser like a zip file or something?
they already are transported compressed, but compression doesn't help ram use, because content needs to be decompressed to use/view

download more ram

>AutoTabDiscard
>Accessibility.force_disabled = 1
Literally all you need! I have 140 tabs open right now and firefox is cruzing on 400mb.

Non-toy web assembly tool chains for major languages. The more plug and play the better.

>what is zram

This

Amazon worked well for me

things are never actually used right out of zram, you put swap on it, only inactive things can reside on swap

OP never said the CPU had to be able to run the compressed code directly.

>Can websites be compressed like on the browser like a zip file or something?
Yes, but the performance impact from that would far outweigh the very marginal memory savings.

>Can websites be compressed
macOS does this for you natively regardless of application

Attached: Screen Shot 2022-06-16 at 10.30.21 PM.png (391x96, 20.52K)

create another new engine for web browser you dummy

I maintain constant use of 2 to 4 browsers at any given time, each of them with at least 20 tabs open, up to like 80 tabs. I have no memory issues. Do you have like 2gb of RAM or what?

I have 32 gb of ram
I still dont like it when a browser, something that has no business going over 1 gb even with 100 tabs, does though

You want something like this?
Come to the Temple and work with us!

Attached: C64_NET.webm (640x480, 1.07M)

Not much actually. Modern browsers implement a fuck ton of stuff nowadays and all that shit gotta be contributing to the memory usage profile. Damn, they even implement MIDI and joystick access, think about it! You can do almost anything through your browser.

>they even implement MIDI and joystick access, think about it!
Why would that need to be in memory while I'm not using it?

By turning them into applications rather than browser tabs.

Site isolation.
firefox-source-docs.mozilla.org/dom/ipc/process_model.html

okay what if someone compiled chrome and took out all but the most bare essential stuff...