this post was submitted on 26 Nov 2024
423 points (100.0% liked)

196

667 readers
102 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Infomatics90@lemmy.ca 7 points 1 week ago (2 children)

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.

[–] jatone@lemmy.dbzer0.com 4 points 1 week ago* (last edited 1 week ago) (1 children)

wat. lol. javascript has nothing to do with the memory consumption. just humans being shitty at their jobs.

[–] Infomatics90@lemmy.ca 6 points 1 week ago (1 children)

I will agree with you that VANILLA JavaScript isn't to blame, but all the frameworks and packages are.

[–] jatone@lemmy.dbzer0.com 4 points 1 week ago* (last edited 1 week ago)

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.

[–] Draconic_NEO@lemmy.dbzer0.com 3 points 1 week ago

Disagreed, memory Limiting definitely helps with over-consumption. Can't consume all the RAM when you only have access to 8GB of it.