News for hackers. Stuff that matters.
Re:Principles of Green Software Engineering by bluGill on Wednesday September 22, 2021 @02:10PM (#28619691)
You have options as a developer. Instead of python/php/perl/ruby (and hundreds of others most of which I don't know) you can write your server side code in C/C++/rust/ada/ (again hundreds of others). You will spend a lot more energy compiling and debugging your code up front, but in the long run you will use less energy on all the server. But will you - every time you roll out an update there are a lot more compiler hours on the developer machines, and less on the server time to amortize it over.

Note that I didn't list managed languages like Java or C#. It isn't clear where they fall - they tend to defer a lot of the CPU until after the user work is done (garbage collection for example). I don't know if anyone has done any fair analysis on this so I'm going to leave it as an exercise for the reader.

Re:Principles of Green Software Engineering by vaughanknight on Thursday September 23, 2021 @11:37PM (#28638362)
In addition there is a need to look at the total cost including supporting functions. Dev test servers, build pipelines, redundancy, failover, deployment environments. Sometimes these may be 5% of emissions, but at other times much higher. And some languages will have significantly less emissions when idle.

A good example here may be, a machine learning model may have 90%+ of it's carbon emissions in the training, vs the operation.