May 19, 2026
Code, cults, and comment chaos
Lisp in Web-Based Applications (2001)
The old coding religion is back, and the comment section is loving the chaos
TLDR: Paul Graham argued that web companies could use unusual programming languages to build faster and outmaneuver bigger rivals. In the comments, fans treated it like vindication for a lost golden age, while others wondered whether this was fresh insight or just another retelling of startup legend.
Paul Graham’s 2001 pitch for using Lisp in web apps reads today like a battle cry from tech’s ancient past: when your software runs on your own servers, he argued, you can pick whatever language helps you move fastest — and a tiny team can absolutely embarrass bigger rivals still clinging to the usual tools. His big flex was speed: build in small steps, keep the site working the whole time, and even fix bugs while the customer is still on the phone. Yes, that part had readers grinning, especially the delightfully mischievous confession that fixing things that fast made it tempting to act like the user had imagined the bug in the first place.
But the real fun is in the comments, where the crowd turns this old essay into a mini culture war. One camp is basically saying, “This wasn’t hype — we lived it.” A commenter recalls tiny Lisp teams crushing better-funded competitors, which gives the whole piece a legend-building, “they don’t make them like this anymore” energy. Another jumps in waving the modern-day revival flag, insisting we’re in “happy times” for Lisp on the web and linking today’s tools as proof that this so-called relic still has fans.
Then there’s the skeptic-curious crowd asking how much of this is genuinely new versus another remix of Graham lore. That tension — timeless insight or recycled startup mythology? — is the real drama. The result is part history lesson, part comeback story, and part comments-section reunion tour for people who still think weird old tools can beat the giants.
Key Points
- •Paul Graham says web-based applications let developers choose any programming language because the software runs on servers they control.
- •The article contrasts older desktop-era constraints, where application languages often followed operating system conventions, with the flexibility of server-side development.
- •Graham presents incremental development as a core Lisp practice: starting with a minimal working program and expanding it while keeping code runnable.
- •He says the Viaweb editor grew from a 120-line website generator to about 25,000 lines of code through gradual change rather than wholesale rewrites.
- •The article states that Lisp’s interactive toplevel helped reproduce bugs from server-side user data and sometimes enabled fixes to be deployed immediately.