What is it about?
You might feel that focusing on carbon-efficiency in software can be misleading because it doesn’t always cut overall emissions. The real goal should be to reduce total carbon in the atmosphere, not just make each unit of software “greener.” However, increasing efficiency isn’t automatically greenwashing. It can guide you toward practical improvements—using less energy or timing your usage when energy is clean—while still being transparent about whether your total emissions actually go down. By measuring both how efficient you are and how much carbon you use overall, you avoid the trap of boasting about small gains while ignoring the bigger picture.
Featured Image
Why is it important?
You might want to read this article because it shows how simply making software “carbon-efficient” isn’t enough to tackle the climate crisis if you ignore total emissions. It addresses the risk of greenwashing, explains why both efficiency and overall totals matter, and explores how good standards can prevent misleading claims. If you’re curious about balancing practical steps with the big picture, it’s worth your time.
Perspectives
I hope to surface some ideas for the efficiency vs. totals debate, how to use efficiency as a metric without slipping into the murky realms of greenwashing.
Asim Hussain
Read the Original
This page is a summary of: Is Software Carbon-Efficiency a Form of Greenwashing?, ACM SIGSOFT Software Engineering Notes, January 2025, ACM (Association for Computing Machinery),
DOI: 10.1145/3709616.3709619.
You can read the full text:
Contributors
The following have contributed to this page