Pfft, everyone knows the cool kids use Lynx.
this post was submitted on 26 Nov 2024
765 points (97.5% liked)
196
16724 readers
2276 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 2 years ago
MODERATORS
Sorry, the only solution is the web aborting JavaScript. never going to happen. trust me, i stand with richard stallman when it comes to javascript.
wat. lol. javascript has nothing to do with the memory consumption. just humans being shitty at their jobs.
I will agree with you that VANILLA JavaScript isn't to blame, but all the frameworks and packages are.
Yes, being shitty at their jobs. even the frameworks/packages are not to blame. its which you pick and how you use them.
for peoples context: just checked a few sites most range in the 30MB-150MB per page. which is pretty reasonable for the complexity of the websites involved. one included a streaming service actively playing a video.
Its just that these things add up across 100 tabs.
Disagreed, memory Limiting definitely helps with over-consumption. Can't consume all the RAM when you only have access to 8GB of it.
What's his stance on javascript? Banned totally on the web?
One could also use w3m or links. All the RAM-hungry things (such as CSS3, JavaScript APIs and heavy multimedia files) will be finally gone for good.
load more comments
(2 replies)
byeah
I mean, you got like a 85% chance that anyone giving you software advice is, closer to 98% for hardware advice.
I still think the catgirl paws salute should be the new salute of the American Résistance.
I also think the catgirl paws salute should be recognized as a salute.
I've been using the Firefox extension "Auto Tab Discard", which helps a lot with RAM usage. I like multi-tab-browsing and IME browsers just don't free up RAM when other applications need them.
wait so you just lose tabs you haven't opened in X mins?
i have a tab sleeping extension & generally throttle the ram with opera
It might be a bit of a misnomer. The tabs aren't deleted, just forcibly unloaded, and you can even prevent it from doing that on a per-tab-basis.
Yeah so it just means the tab's going to need to refresh when you click back to it. That seems perfect honestly, it's already what most phone browsers do more aggressively. Cheers :)
I tried that but I found that its effects on long term memory leakage weren't adequate for me, and it still consumed way too much RAM. Which is why I just decided to limit RAM for Firefox. It achieves a similar effect as the browser unloads tabs when it runs low on memory, it just doesn't wait until it's using 31GB of RAM and instead just uses up to 8GB (which is what I capped it at) before unloading tabs.