On Lobste.rs home there’s yet another article commenting on the sad state of something. This is a quite common way of thinking about ecosystems, communities, tools and entire sectors that utterly disfunctional. IT is ripe for these kind of considerations because indeed, most software is written in contexts that prioritize profit, success or social credit over reliability, accessibility, sustainability, portability, inclusivity, resilience and the ability of your software to age well and grow. We get it, IT is shit, software is broken, but there must be a case of success that we can take inspiration from. Therefore I ask you what is, according to you, a field, a context, an environment, an ecosystem, where quality and good software manage to produce meaningful software with an impact on the world, and why you think they differ from the rest of IT. Some rules to avoid boring answers:
it must be software that is in some way relevant it cannot be a single project: python’s requests, the linux kernel etc etc don’t qualify if they are pearls in the mud. they must be mature enough to have encountered some kind of challenge. Rust’s ecosystem is old enough to qualify, the latest functional language produced by a Latvian university that is used by 4 people to implement Peano’s arithmetics in the type system doesn’t qualify.