December 7, 2025

Bring your 3D glasses (and receipts)

The programmers who live in Flatland

Lisp fans claim ‘3D coding’ powers; skeptics say ‘prove it’

TLDR: An essay says Lisp/Clojure lets programmers work in a “third dimension,” reshaping code before it runs. Commenters fired back: some want concrete, real-world examples, others argue language choice rarely decides success, and jokers posted spacey links—netting a simple ask: less mystique, more proof people can use.

Today’s spicy dev debate: a Lisp-loving author says many coders are stuck in “Flatland,” unable to see a magical third dimension where Clojure (a modern Lisp) lets code write code. Citing Paul Graham’s famed Beating the Averages, they argue macros—little programs that reshape your program before it runs—unlock superpowers most languages can’t touch. The post calls parentheses “weird” complaints a distraction and claims the real leap is controlling compile time like clay. Translation: learn this, and you’ll ship cleaner, smarter software while everyone else doodles in 2D.

But the comments? Absolute fireworks. One reader all but slammed the brakes: “it’s not beyond our comprehension… so… do that…”—show proof, not parables. Another demanded receipts: “Show me… material outcomes that I will care about.” The pragmatists chimed in with a reality check: maybe the “higher-dimensional move” is admitting language choice rarely decides success. Meanwhile, an old-school nod to Alan Kay’s ants-on-planes metaphor added homework vibes, and a joker derailed the thread with a 1D spaceship in Game of Life. Verdict: macro evangelists vs results-first skeptics vs “use whatever works” pragmatists. The only thing everyone agreed on? If there’s a 3D world here, the door needs a handle—examples, not sermons.

Key Points

  • The article uses Flatland as a metaphor to describe differing “dimensions” of programming abstractions.
  • It cites Paul Graham’s 2001 essay claiming Lisp’s macros provided Viaweb competitive advantages and introduces the blub paradox.
  • The author argues that Lisp/Clojure adoption is low due to misconceptions, including ecosystem concerns and syntax aversion.
  • Clojure is presented as interoperating with a large ecosystem and offering transformative approaches to state and identity.
  • Lisp/Clojure macros are described as enabling compile-time logic and syntax tree transformation, adding a new dimension to programming.

Hottest takes

"it's not beyond our comprehension... so... do that..." — parpfish
"the true higher-dimensional move is realizing that choice of programming language isn’t usually the critical factor" — libraryofbabel
"Show me. Specifically, material outcomes that I will care about." — hashmap
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.