I could have easily given an example of a web page that uses a ton of CPU while idle. But a contractor built it on may company’s website years ago and it’s not a priority to fix it. While I don’t know or care if it truly “maxed” the CPU, that wasn’t the point at all. The point was that it was a WEB PAGE, which a lot of people noticed that while sitting practically idle (a very simple animation playing) caused laptop fans to spin up like crazy.
But my slight exaggeration (using the word “max”) aside, the point was that any software can run inefficiently and that even small differences could add up to significant energy waste when deployed to millions of users.
I’m not sure why you’d make a claim that a PDF viewer could never be inefficient enough to matter. Of fucking course it could. Unless you have completed a study proving otherwise, you’re just talking out of your ass, and it’s a really weird hill to die on.
Mate, we are talking about international / widely used websites here. Of course you can build a shit website that eats up resources, I can do that in a single line of code. But the average website out there doesn’t burn up resources for no reason at all, most content is static and just sits there after being loaded.
Open up any PDF viewer you like, whatever you think is the heaviest or shittiest one (Probably Adobe). Load a big pdf file, now check the resource usage. It’s going to be absolutely nothing, any Electron app (like Discord) eats up way more RAM and CPU time.
Now get out with your straw man argument, you derailed this whole conversation by going from pdf readers to websites with this comment:
You say this but devs are making webpages that max out cpu usage when nothing is actually happening to render the webpage, it’s just rerendering stuff unnecessarily because hardware is cheap and no one is calling them on it.
I could have easily given an example of a web page that uses a ton of CPU while idle. But a contractor built it on may company’s website years ago and it’s not a priority to fix it. While I don’t know or care if it truly “maxed” the CPU, that wasn’t the point at all. The point was that it was a WEB PAGE, which a lot of people noticed that while sitting practically idle (a very simple animation playing) caused laptop fans to spin up like crazy.
But my slight exaggeration (using the word “max”) aside, the point was that any software can run inefficiently and that even small differences could add up to significant energy waste when deployed to millions of users.
I’m not sure why you’d make a claim that a PDF viewer could never be inefficient enough to matter. Of fucking course it could. Unless you have completed a study proving otherwise, you’re just talking out of your ass, and it’s a really weird hill to die on.
Mate, we are talking about international / widely used websites here. Of course you can build a shit website that eats up resources, I can do that in a single line of code. But the average website out there doesn’t burn up resources for no reason at all, most content is static and just sits there after being loaded.
Open up any PDF viewer you like, whatever you think is the heaviest or shittiest one (Probably Adobe). Load a big pdf file, now check the resource usage. It’s going to be absolutely nothing, any Electron app (like Discord) eats up way more RAM and CPU time.
Now get out with your straw man argument, you derailed this whole conversation by going from pdf readers to websites with this comment:
What a fucking moron