3 ms·
> Running your site in a container on a shared host will be significantly more energy efficient then running hardware. It's silly to claim otherwise. Probably
by throwaway894345 6y ago
> Running your site in a container on a shared host will be significantly more energy efficient then running hardware. It's silly to claim otherwise.
Probably not. Running your own hardware implies more total hardware because you're not going to be able to saturate your hardware as efficiently as Amazon/Google/MS/etc. Moreover, you'll need to hire more people to work on that hardware (doing the work that Amazon/MS/Google do for you--and let's not pretend that cloud provider work is trivial).
That said, I don't exactly understand the calculus here because it's not like you're creating people who wouldn't otherwise exist for the sole purpose of operating your hardware.
> The issue is how many computations you do at runtime. That is completely unrelated to third party libraries.
Presumably the logic is that third-party libraries cause bloat, and bloat that needs to be sent to the client every time they reload your page (modulo cache hits). And it's certainly far more energy intensive to send a megabyte across a continent than to load it from memory into CPU cache or whatever.