3 ms·

Docker and Kubernetes are the worst offenders then. Modern DevOps often fire up a separate container for the smallest service. Another huge chunk of the "pollut

by xvilka 7y ago

Docker and Kubernetes are the worst offenders then. Modern DevOps often fire up a separate container for the smallest service. Another huge chunk of the "pollution" is the bytecode and interpreted languages. Getting rid of the languages and VMs without AOT-compilation will reduce the carbon footprint a lot.

unrealhoang 7y ago
Nah, before that they was spawning a whole new VM for a service as well, it’s low quality programming to blame, not the tools.
- t-writescode 7y ago
  Not really, no. At least, not at my old company. My team had a set of machines for a multitude of scheduled tasks and jobs.
- rusticpenn 7y ago
  The biggest problem we face is that the number of programmers we need is much higher than the actual, available programmers. We are becoming more and more efficient everyday. One of the projects I work with has us converting 200+ excel sheets on 20 different computers into one CRUD microservice and a frontend. The biggest problem? convincing the people to move away from excel.
dnautics 7y ago
Man you should see what the CPU does. It's basically JITting your asm, and dropping the calculation result off. executing your code twice (once for branch prediction), putting things out of order,
- saagarjha 7y ago
  Hey, if it gives you a short time-to-idle…
tannhaeuser 7y ago
You're being downvoted because your comment hits too close to home here. Regarding Docker (which I hate like the plague when it's being naively used for "microservices" as an excuse for architecture by the infanterists of our profession), an argument could be made that it helps density in data centers such that fewer physical machines and VMs need to run all the time, though I believe this is offset by network overhead, ruining any advantage it may have when considering total energy consumption. Regarding overuse of webapps and JavaScript, though, there's really no excuse for the React and co overkill. Apple, Google, and Firefox should display a little indicator/traffic light of sorts warning about high energy use. Google could also flag/penalize the worst offenders in search results, etc.

by xvilka 7y ago

unrealhoang 7y ago

Nah, before that they was spawning a whole new VM for a service as well, it’s low quality programming to blame, not the tools.

t-writescode 7y ago
Not really, no. At least, not at my old company. My team had a set of machines for a multitude of scheduled tasks and jobs.
rusticpenn 7y ago
The biggest problem we face is that the number of programmers we need is much higher than the actual, available programmers. We are becoming more and more efficient everyday. One of the projects I work with has us converting 200+ excel sheets on 20 different computers into one CRUD microservice and a frontend. The biggest problem? convincing the people to move away from excel.

dnautics 7y ago

Man you should see what the CPU does. It's basically JITting your asm, and dropping the calculation result off. executing your code twice (once for branch prediction), putting things out of order,

saagarjha 7y ago
Hey, if it gives you a short time-to-idle…

tannhaeuser 7y ago

You're being downvoted because your comment hits too close to home here. Regarding Docker (which I hate like the plague when it's being naively used for "microservices" as an excuse for architecture by the infanterists of our profession), an argument could be made that it helps density in data centers such that fewer physical machines and VMs need to run all the time, though I believe this is offset by network overhead, ruining any advantage it may have when considering total energy consumption. Regarding overuse of webapps and JavaScript, though, there's really no excuse for the React and co overkill. Apple, Google, and Firefox should display a little indicator/traffic light of sorts warning about high energy use. Google could also flag/penalize the worst offenders in search results, etc.