|
|
|
|
|
by fiddlerwoaroof
787 days ago
|
|
This is one of those perpetual myths about macros. Ruby on Rails metaprogramming is often harder to debug than macros in Common Lisp. Flink and Spark work by generating and loading Java code at runtime (macros) but, since Java has no language-level support for macros, the generated code is very hard to inspect and debug. What killed most lisps was the AI Winter and the concurrent drying up of DARPA funding. |
|
When I say software at scale I mean:
- going on GitHub opening a file and understanding what's happening
- reviewing a PR and figuring out stuff without requiring an ide
- having easy onboarding with devs already accustomed to a base language and its patterns
Java, C, TypeScript, Scala, Kotlin, etc. Pretty much all major languages offer this: less power but much less ambiguity and mental overhead.
Lisps (with a minor exception for clojure) and Haskell are just not those languages.
Which, again, is why all of those languages produced very little software worth of mentioning for decades.