August 10, 2026
Syntax and the City
Because It's Not Fun Enough: why languages fail
The real reason coding languages die? Devs ditch anything that feels like homework
TLDR: The article argues coding languages don’t win because they’re superior — they win because people and companies actually want to use them. Commenters turned that into a drama-fest about AI, JavaScript vs. Python, and whether calling Objective-C a flop is flat-out insulting.
A deceptively thoughtful essay about why coding languages live or die has sparked a very online identity crisis: are these tools supposed to help people earn a living, make cool things, or simply enjoy the craft? The article’s big idea is that the winners aren’t always the “best” ones. They’re the ones people can actually stand using — and the comment section absolutely ran with that. One reader said the whole thing secretly explains AI coding tools too: great if you just want output, awful if you actually like the act of making something. That hit a nerve.
Then came the inevitable food fight over which languages belong in the winners’ circle. One commenter dropped the wonderfully chaotic hot take “Boom: JavaScript. Bust: Python,” basically lobbing a grenade into the room and walking away. But the loudest backlash was over Objective-C being called a “false start.” That description was treated like a personal insult to Apple history, with one defender fuming that a 40-year-old language used to build NeXTSTEP, Mac OS X, and iPhone apps does not qualify as some embarrassing misfire.
The mood was part philosophy seminar, part fandom war. People agreed on one thing, though: success in tech is often less about elegance and more about momentum, money, habits, and whether a tool makes people miserable. In other words, the nerds have spoken: if it feels like homework, it’s cooked.
Key Points
- •The article centers on Andrew Oram’s Linux Professional Institute series about why programming languages rise and fall.
- •It identifies Simon Peyton Jones’s statement that adoption is only weakly connected to technical merit as the article’s key explanatory idea.
- •The article argues that language adoption depends on both technical and human factors, especially whether a language works as a vocation, an art, and a job.
- •It classifies some languages by failure mode: Pascal and Tcl as poor for daily work, Ada and PL/I as mandate-driven, and Perl and Haskell as limited by market or intentional adoption choices.
- •It uses JavaScript and Objective-C as examples showing that platform position and ecosystem context can preserve adoption despite perceived awkwardness.