Our Code Is Harming the Planet, We Need Carbon Aware Design Patterns

With all the bloat-tastic web sites there are these days... What if a browser or plug-in displayed a little animated &quot;Electric Meter&quot; icon, which showed how power-sucking the site you were currently viewing was? With a few customization options (title, colors) users could re-label it as &quot;battery sentry&quot;, &quot;bill miser&quot;, &quot;earth saver&quot;, or whatever floated their boat.<p>Seems like something that could really appeal to Joe Average User.

Pointless animation on that page - wasting cycles - needless carbon spent. Vile hypocrites.

This is not a code issue, everything that use power is harming the planet, but the solutions listed there are not to write better&#x2F;different code but simply switch the times and other things that only mitigate the problem.<p>Anyway better than nothing.

Delivered by a page needing 4+ Mb for something that&#x27;s mostly just text. Well done showing us how to save the planet!

It looks like most comments here ridicule the idea. I think it&#x27;s something that for some reason is discussed more in Europe than in the USA.<p>Basically, the point here is that (1) if any given computation can be performed in several ways, and one of them consumes less energy, you should strive to use it, (2) if you can get a similar result by using significantly less energy, you should consider it.<p>The reason for that is the scale: at this point we can not ignore the fact that the number of computing machines in everyday use is so high that even small changes that impact a large number of them also impact the whole environment. So obviously we are talking mainly about biggest players mainly. But not only: if your small library or app becomes so popular everybody starts to use it, you can make a difference, too (plus your users will love you - nobody likes resource hogs).

Here&#x27;s an example of how an existing (and maybe the oldest?) language but with &quot;new armor&quot; can significantly lower the carbon footprint:<p>Writing Green Software - Is Our Code Unfriendly to Environment - <a href="https:&#x2F;&#x2F;dev.to&#x2F;velydev&#x2F;writing-green-software-is-our-code-unfriendly-to-environment-4an6" rel="nofollow">https:&#x2F;&#x2F;dev.to&#x2F;velydev&#x2F;writing-green-software-is-our-code-un...</a>

Drops in the bucket while data-centers burn most of their consumed power in cooling, ups bleed, and idle unused capacity before a single line of code is run.

<a href="https:&#x2F;&#x2F;dl.acm.org&#x2F;doi&#x2F;10.1145&#x2F;3533028.3533308" rel="nofollow">https:&#x2F;&#x2F;dl.acm.org&#x2F;doi&#x2F;10.1145&#x2F;3533028.3533308</a> A paper where the authors use machine learning (ML) to optimize latency and hardware usage of Apache Flink dataflow programs. There&#x27;s a paper in preparation from the same authors where they&#x27;re looking at ML to reduce energy usage.

Nice to see an article on environmental impacts but it seems to be missing the &quot;approach&quot; of simply using less energy.. For example:<p>1. Generating less logs &amp; expiring them more quickly 2. Including fewer third-party SDKs 3. Using lower-resolution images &amp; videos 4. Not encouraging people to buy unnecessary goods through marketing..

Clickbait title. The article is not about writing carbon-aware code, but about where to run large-scale applications.

As another poster said, that isn&#x27;t a code issue.<p>You know what is a code issue though? &quot;I dun need no optimazashun, I&#x27;m a faithful beleevur in Moore&#x27;s Law, in the fuchur ppl will run my junk XD&quot;. Every single of those needless operations that your software does consumes electricity, without actually improving the life of anyone. Those will pile up because it isn&#x27;t just you, it&#x27;s software developers from the whole world doing this kind of stuff, with software run by almost everyone in the world.<p>It&#x27;s fine to not care too much about efficiency when you&#x27;re just solving some local issue with a dirty bash script, that you&#x27;ll run exactly once and forget about it. However, software developers should have a bit more insight that needlessly wasting everyone&#x27;s electricity.

Use compiled binaries everywhere! End the hegemonic AntiGreen opression of dynamic languages! ;) . CORE - compile once, read everywhere is here to save us

Use Nim instead of Rust and C++. Shorter compile times.

Problem: cloud computing is hurting the environment.<p>Solution: a new cloud computing service to add on top of your existing cloud computing services.<p>Brilliant.