The article titled “The green software that could make big carbon savings” highlights the challenges posed by the rapid obsolescence of technology and the environmental consequences tied to upgrading electronic devices. It begins with the anecdote of Waseem Mirza, an actor and presenter who found himself frustrated upon realizing that his Samsung phone, still functioning perfectly, would not receive security updates from 2020. Mirza’s narrative emphasizes not just the personal inconvenience but also the environmental costs associated with the persistent cycle of technological upgrades. Citing that approximately 80% of carbon emissions from mobile phones stem from their manufacturing (termed as embedded or embodied carbon), the article notes that prolonging the lifespan of existing devices can lead to substantial emissions reductions.
Transitioning to a potential solution, the article introduces /e/OS, a free Android variant designed to revive older smartphones that no longer receive manufacturer support. This operating system extends the operational life of devices, allowing users like Mirza to benefit from security updates while minimizing their ecological footprint. Gaël Duval, the founder of /e/OS, explains that their software aims to optimize older devices by reducing bloatware, which typically slows down performance while making efficient use of resources. Devices like Mirza’s Galaxy S7 Edge, which is soon to be unsupported due to hardware limitations, could achieve an additional five years of use through /e/OS.
Software longevity is not only crucial for minimizing electronic waste but is also increasingly recognized by major manufacturers. For instance, Samsung has extended its support for new devices to seven years, while Apple has committed to providing a minimum of five years of support for its iPhone 16. According to Rik Viergever, COO of /e/OS, advancements in technology suggest that newer models could remain functional far beyond their guaranteed support period.
Beyond device longevity, the article delves into the broader implications of software energy efficiency. It refers to the considerable energy consumption associated with server-based applications, contrasting it with mobile apps that must remain battery-efficient. This acknowledgment leads to the introduction of the Software Carbon Intensity (SCI) specification, crafted by the Green Software Foundation to quantify the carbon footprint of software. Asim Hussain, the executive director of the foundation, emphasizes the challenges developers face in measuring carbon intensity due to limited tooling available for optimization. The goal of the SCI is to offer a score that helps developers track their emissions reductions over time.
Despite these advances, accurately calculating the SCI remains complex, according to Hussain. The Green Software Foundation has created a tool named the Impact Framework to estimate carbon emissions based on observable server resource usage and other factors. Notably, Hussain encourages CTOs to foster a culture of transparency and feedback surrounding this data, suggesting that developers will improve emissions metrics if given strong performance indicators, even if initial attempts may not succeed.
Additionally, the article mentions the ecoCode project, which focuses on refining code for energy efficiency by identifying potential resource-intensive practices typically referred to as “code smells.” Tariq Shaukat, CEO of Sonar, notes that many code smells derive from complexity, inefficient operations, and excessive bloat—issues that developers can address through streamlined coding practices.
The discussion also touches on the pressing nature of climate change in relation to the ICT sector, which was estimated to contribute 1.4% to greenhouse gas emissions in 2020, a figure projected to rise to 14% by 2040. Encouragingly, larger enterprises appear to be acknowledging this growing concern, with predictions suggesting an increase in software sustainability requirements from 10% to 30% by 2027.
In conclusion, the article illuminates the dual challenges of technological sustainability and carbon emissions in the software industry. The advancements showcased—from Waseem Mirza’s quest for a longer-lasting phone solution to the framework and tools developed for reducing the carbon impacts of software—demonstrate a gradual shift toward a greener future in technology. As the industry continues to evolve, the necessity for developers and manufacturers to prioritize sustainability alongside innovation has never been clearer.
