April 29, 2026
Parentheses, pride, and a tiny civil war
Why I still reach for Lisp and Scheme instead of Haskell
Coder picks old-school Lisp over Haskell and the comments instantly split into teams
TLDR: The writer says Haskell is beautiful but too fussy for quick real-world work, so they still reach for Lisp and Scheme. In the comments, fans fought over flexibility versus safety, with one side praising live fixes and the other warning that Lisp can become unreadable fast.
A programmer walked into the internet and basically said: yes, Haskell is brilliant, but when I actually need to build something fast, I still grab Lisp or Scheme. That was enough to light up the comment section like a family dinner gone wrong. The author’s big point was simple: one language feels like a beautiful, elegant puzzle box, while the other feels like a practical workshop where you can just start making things. For regular humans, that means this isn’t really about “best language” at all — it’s about whether you want perfection or momentum.
And the crowd had opinions. One camp swooned over Lisp’s legendary flexibility, with people hyping its ability to reshape itself and even fix running programs live — yes, commenters were openly giddy about the idea of patching software in production, which sounds either magical or like the start of a disaster movie. Another group was not buying the romance at all, arguing that Haskell’s stricter style makes code safer and cleaner, while Lisp’s macro tricks can turn programs into unreadable chaos. Then came the drive-by psychoanalysis: one commenter shrugged and said the whole debate is basically about syntax — if you like the look and feel, you’ll defend it forever.
There was even a cheeky matchmaking moment when someone read the author’s complaints and declared, essentially, “You don’t want Scheme or Haskell — you want Clojure”. Classic comment-section energy: part advice, part ambush, fully entertaining.
Key Points
- •The article examines a recurring tradeoff in software engineering between mathematically elegant programming models and practical productivity.
- •It presents Haskell as powerful for type-driven and functional programming, highlighting its advanced type system and its role in popularizing concepts such as monads and functional DSLs.
- •It argues that Scheme and Lisp provide a more flexible and pragmatic environment for rapid prototyping and exploratory development.
- •The article uses a bookmark-management prototype as an example, describing difficulty in Haskell when trying to transform data models to XML and write them to a file.
- •It contrasts Haskell’s friction in that example with the relative ease of accomplishing similar XML tasks in Java or Kotlin using common tools such as Gradle, Jackson, or a DOM parser.