▲ 76 ▼ Designing Firefox for the future (blog.mozilla.org) submitted 5 months ago by sabreW4K3@lazysoci.al to c/firefox@lemmy.ml 54 comments fedilink hide all child comments
[–] SapphironZA@sh.itjust.works 17 points 5 months ago (6 children) Make it do less, a LOT faster, using less resources, with good extension support. That is a good browsers only job. permalink fedilink source hideshow 6 child comments replies: [–] tb_@lemmy.world 2 points 5 months ago (3 children) If that were the entire truth, neither brave nor opera would be as popular as they are. permalink fedilink source parent hideshow 3 child comments replies: [–] SapphironZA@sh.itjust.works 1 point 5 months ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] BigTechMustBurn@lemmy.ml 1 point 5 months ago (1 child) Because in the 2000s websites were primarily HTML and CSS and not the Javascript abominations we have today. permalink fedilink source parent hideshow 1 child comment replies: [–] SapphironZA@sh.itjust.works 1 point 5 months ago Its not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose. permalink fedilink source parent [+] racoon@lemmy.ml -2 points 5 months ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] SapphironZA@sh.itjust.works 8 points 5 months ago You might want to add a little /s there. But yes, decisions made by people who dont pay for their own hardware. permalink fedilink source parent
[–] tb_@lemmy.world 2 points 5 months ago (3 children) If that were the entire truth, neither brave nor opera would be as popular as they are. permalink fedilink source parent hideshow 3 child comments replies: [–] SapphironZA@sh.itjust.works 1 point 5 months ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] BigTechMustBurn@lemmy.ml 1 point 5 months ago (1 child) Because in the 2000s websites were primarily HTML and CSS and not the Javascript abominations we have today. permalink fedilink source parent hideshow 1 child comment replies: [–] SapphironZA@sh.itjust.works 1 point 5 months ago Its not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose. permalink fedilink source parent
[–] SapphironZA@sh.itjust.works 1 point 5 months ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] BigTechMustBurn@lemmy.ml 1 point 5 months ago (1 child) Because in the 2000s websites were primarily HTML and CSS and not the Javascript abominations we have today. permalink fedilink source parent hideshow 1 child comment replies: [–] SapphironZA@sh.itjust.works 1 point 5 months ago Its not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose. permalink fedilink source parent
[–] BigTechMustBurn@lemmy.ml 1 point 5 months ago (1 child) Because in the 2000s websites were primarily HTML and CSS and not the Javascript abominations we have today. permalink fedilink source parent hideshow 1 child comment replies: [–] SapphironZA@sh.itjust.works 1 point 5 months ago Its not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose. permalink fedilink source parent
[–] SapphironZA@sh.itjust.works 1 point 5 months ago Its not so much the JavaScript, its the layers and layers of JavaScript libraries that are never optimized or trimmed for purpose. permalink fedilink source parent
[+] racoon@lemmy.ml -2 points 5 months ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] SapphironZA@sh.itjust.works 8 points 5 months ago You might want to add a little /s there. But yes, decisions made by people who dont pay for their own hardware. permalink fedilink source parent
[–] SapphironZA@sh.itjust.works 8 points 5 months ago You might want to add a little /s there. But yes, decisions made by people who dont pay for their own hardware. permalink fedilink source parent