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.
wat. lol. javascript has nothing to do with the memory consumption. just humans being shitty.
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.