| Hi there, I'm terrible at addressing the current environmental challenges. This morning, I discovered the Website Carbon Calculator [0] and tested all the websites I've created. To my surprise, some of my websites turned out to be disastrous. Until now, I hadn't been concerned about the carbon footprint of my apps, but having access to this information encourages us, as developers, to take responsibility for the performance of what we build. This article [1] details how to reduce this footprint when building websites, serving as a great starting point for considering how we can minimize our impact (e.g. using less JavaScript) I don't want to engage in the cliché of “greenwashing”, but rather aim to make a positive impact as a developer. What are your thoughts? Were you already aware of this? [0] https://www.websitecarbon.com/ [1] https://www.wholegraindigital.com/blog/website-energy-efficiency/ (I'm not affiliated with any of the website I quote) |
We are collectively rewriting desktop apps to run in the browser, where not only it runs 50x slower than on the desktop, but all data has to be downloaded time and again from servers. The amount of waste here is staggering. And yet, desktop apps have so many issues (installation/breakage/crashes) that web apps are the only way to deliver software that just works.
Web developers can, and should, build light and fast websites. But the average person runs spotify, youtube, netflix and other streaming services pretty much 24/7. A slightly faster personal blog isn’t even a drop in the bucket.
And waste from computing, bad as it may be, pales into comparison to the waste of a “quick trip to the store” with a 4 ton truck.
As software engineers the best thing we can do is to write good software that lasts and that solves real problems. Climate guilt really doesn’t come into play here.