Is Clojure an acceptable Lisp?
summary
Argues that Common Lisp keeps homoiconicity and REPL-driven development with full dynamic scope, condition handlers and CLOS with a CLOS metaobject protocol for runtime metaprogramming; shows how declarations, disassembly and image dumping give near-zero startup and predictable native performance. Contrasts that Clojure offers persistent value semantics, JVM JIT speed, safe hosted execution and Maven-backed libraries and community consistency, and concludes Clojure wins for everyday production while Common Lisp wins for low‑level systems and interactive metaprogramming.
AI-written summary · about
chapters (23)
- 0:00Hans introduction
- 2:07Steve Yeager
- 3:04Sweet McCarthy
- 3:39The essence of Clojure
- 4:07Data structures
- 5:31Interactive mode
- 6:43What is commonlist
- 7:25Why is commonlist created
- 8:53Commonlist implementations
- 10:10Keyword arguments
- 12:03Dynamic scope
- 14:05Object system
- 16:40Meta object protocol
- 18:37Supporting the user
- 21:20Disassembly
- 22:14Debuggers
- 22:58Startup
- 25:02Surface Syntax
- 25:20Value Semantics
- 27:06Hosted Language
- 27:35Clojure Libraries
- 29:11Conclusion
- 29:46Clojure is live forever
