@tbernard Thank you for this interesting series.

It is weird, to me the conclusions on how software should be designed in face of climate crisis, environmental crisis, pandemic, and war, sound like ways to make generally reasonable software that doesn't suck.

I can imagine that your position is not very established, but it presents an interesting "softening" of more radical perma computing or collapse computing ideas.

Wanting to limit excess in all areas, including computing, is great. Yet in a way, a typical 738 MB Electron to do list app is as much overspecced as a project creating an operating system that can run on a Furby dug out from the rubble in a postapocalyptic world is "negatively overspecced."

The stylish cyberpunk doomsday scenarios are kind of easy to co-opt and fraudulently addressed by big tech products, while an established practice of making reasonable software is much harder to compromise. Continuity is the biggest enemy of disruption :) So I much welcome this investigation of photo apps and syncing data over unstable connections.

Related, here's my favorite critique of the "Arctic Code Vault" as a negatively overspecced project to save computing after the collapse: https://blog.dshr.org/2019/11/seeds-or-code.html