My Software North Star

A programmer posted a calm, almost philosophical mission statement: build software that is useful, correct, and easy to maintain, with one big rule above all else — the user comes first. In plain English, the author says fancy tools, pretty code, and even built-in safety features don’t mean much if the end result is broken, slow, impossible to fix, or hostile to the people using it. Sounds reasonable, right? The comments immediately said: absolutely not, let’s fight.

The biggest drama came from readers who felt this was a thinly veiled swipe at Rust, a popular programming language with a reputation for safety. One commenter basically accused the author of sounding weirdly bitter, arguing that safety guardrails obviously matter even if your process isn’t perfect. Another zoomed out and turned the whole thing into community therapy, saying it must be a rough time to be a Zig fan — especially after Bun famously moved from Zig to Rust to deal with memory problems. Ouch.

But not everyone came for blood. Some readers found the post genuinely inspiring, praising the people building Zig and celebrating the author’s passion. Others took the discussion into comedy-philosophy territory, with one delightfully cursed take claiming there’s no meaningful difference between features and bugs. Meanwhile, another commenter latched onto the word “useful” like it was the final boss, asking: useful to whom, exactly? So yes, the article was about software values — but the real show was a comment section split between admiration, existential nitpicking, and language-war shrapnel.