sabreW4K3@lazysoci.al to Firefox@lemmy.mlEnglish · 2 months agoDesigning Firefox for the futureblog.mozilla.orgexternal-linkmessage-square59fedilinkarrow-up180file-text
arrow-up180external-linkDesigning Firefox for the futureblog.mozilla.orgsabreW4K3@lazysoci.al to Firefox@lemmy.mlEnglish · 2 months agomessage-square59fedilinkfile-text
minus-squareSapphironZA@sh.itjust.workslinkfedilinkarrow-up1·2 months agoIn my assessment, all browsers suck badly at performance and resource usage at the moment. How does a 25mb website content result in 350mb of ram usage for that tab? And why would it not render basically instantly. I am old enough to remember in the early 2000s, when page loads were near instant. Even for large e-commerce and social media websites.
minus-squareBigTechMustBurn@lemmy.mllinkfedilinkarrow-up1·2 months agoBecause in the 2000s websites were primarily HTML and CSS and not the Javascript abominations we have today.
minus-squareSapphironZA@sh.itjust.workslinkfedilinkarrow-up1·2 months agoIts not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose.
In my assessment, all browsers suck badly at performance and resource usage at the moment.
How does a 25mb website content result in 350mb of ram usage for that tab? And why would it not render basically instantly.
I am old enough to remember in the early 2000s, when page loads were near instant. Even for large e-commerce and social media websites.
Because in the 2000s websites were primarily HTML and CSS and not the Javascript abominations we have today.
Its not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose.