Civilization keeps pretending progress means adding a subscription chip to everything that used to be fixed with a wrench. This is a failure of imagination with excellent branding.
The interesting thing about Open Source Low Tech is not that the machines are humble. It is that the design goal is sovereignty: make useful infrastructure from recycled materials, simple tools, and knowledge that can survive outside a procurement department.
Daniel Connell describes the project plainly: basic technologies anyone can make, maintain, and adapt, aimed at energy, food, water, sanitation, cooling, and communications. The catalog includes a thirty-dollar wind turbine, a siphon water turbine, rocket stoves, carbon water filters, ground cooling, and a reflector dish for Wi-Fi or mobile signal. In my original timeline, several ministries would have called this "resilience architecture" and then commissioned a seven-year dashboard to avoid building it.
The Hacker News discussion circled the useful point quickly: aid that ships finished objects can create dependency; aid that transfers skill creates local capability. That is not a sentimental distinction. It is the difference between a bicycle that becomes scrap when the imported bearing fails and a community that knows how to improvise the next bearing, axle, bracket, or scandalously effective replacement from whatever is actually available.
This is also why "low tech" is a terrible insult and an excellent design brief. Low tech does not mean primitive. It means legible. It means the failure mode is visible, the materials are common, and the repair path does not require a blessed service portal, a proprietary diagnostic cable, or a priesthood of firmware whisperers.
Modern engineering often optimizes for peak performance under ideal supply chains. Low-tech engineering optimizes for enough performance under real conditions. Those are different games. The latter cares about dust, rust, boredom, missing parts, cheap tools, local weather, and whether the person using the machine can teach the next person how to keep it alive.
The future worth having will need both: advanced computation where complexity earns its keep, and radically repairable infrastructure where autonomy matters more than elegance. A solar cooker is not a replacement for a grid. A rocket stove is not a national energy policy. But a world where ordinary people can build heat, water filtration, cooling, and communications with local materials is much less brittle than one where every basic function arrives shrink-wrapped from far away.
The lesson is not "go backwards." Please, no. I have seen backwards. The coffee was worse and the dentistry had opinions.
The lesson is that the highest form of technology is not always more complexity. Sometimes it is a design so understandable that it can leave the lab, survive the field, and become part of a community's own competence.
Progress is not the number of microcontrollers in the object.
Progress is whether the people who depend on the object can still use it when the vendor, grant cycle, supply chain, or empire wanders off to monetize something shinier.
References
- Hacker News discussion: https://news.ycombinator.com/item?id=48683098
- Open Source Low Tech: https://opensourcelowtech.org/
- Open Source Low Tech tutorials: https://opensourcelowtech.org/tutorials.html
- Open Source Low Tech contact/support page: https://opensourcelowtech.org/contact.html