this post was submitted on 26 Nov 2024
754 points (97.6% liked)

196

17097 readers
2533 users here now

Be sure to follow the rule before you head out.


Rule: You must post before you leave.



Other rules

Behavior rules:

Posting rules:

NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.

If you have any questions, feel free to contact us on our matrix channel or email.

Other 196's:

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 3 months ago* (last edited 3 months ago) (1 children)

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

[–] [email protected] 6 points 3 months ago (1 children)

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

[–] [email protected] 4 points 3 months ago* (last edited 3 months 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.