June 30, 2026
Syntax Wars: Short, Loud, Petty
Stroustrup's Rule (2024)
Why coders beg for extra words at first, then demand shortcuts later
TLDR: The article says people learning a programming language want clear, wordy code, but experienced users eventually prefer quick shorthand. In the comments, readers fought over whether that idea is too simplistic, with others nitpicking the name itself and reviving years-old debate like it never ended.
A programming essay about why beginners want everything spelled out and veterans want sleek shortcuts somehow turned into a full-on comment-section identity crisis. The core idea, nicknamed Stroustrup’s Rule, is simple: when a tool or feature is new, people want loud, obvious wording; once they know it well, they start begging for shorter ways to write the same thing. The article points to examples from Rust error handling and Python’s infamous “walrus operator,” basically the coding version of people saying, “Please explain every step” and then, five years later, “Why is this so verbose?”
But the real fireworks were in the reactions. One camp said the rule is too neat and too cute to explain the messiness of real software design. MarkusQ jumped in with the “missing dimension” argument: it’s not just about long versus short, it’s about whether a feature behaves cleanly on its own or creates chaos when mixed with everything else. Another commenter wanted the theory edited for accuracy, arguing people only demand shorthand for features they end up using all the time. And then came the pedants — because of course they did — with one commenter insisting this isn’t even a “rule,” it’s an observation. Yes, the community really stopped the presses to litigate the job title of the sentence.
The funniest vibe? A low-key “we’ve been arguing about this forever” energy, complete with someone resurfacing an old Hacker News thread like a reality show reunion episode. In other words: the syntax debate is eternal, everyone is annoyed, and everyone is also somehow proving the article right
Key Points
- •The article presents Stroustrup’s Rule as the idea that new language features tend to require explicit syntax, while established features tend to gain terser notation.
- •Rust error handling is used as an example, moving from explicit `match` statements to the `try!` macro and then the `?` operator.
- •The author frames the rule as part of mental model development: beginners need more explicit information, while experienced programmers find it to be visual clutter.
- •The article says programming language communities also shift toward expert-friendly syntax over time as the proportion of experienced users increases.
- •In teaching TLA+, the author prefers more explicit invariant notation for beginners even though experts favor a terser function-set formulation.