Thoughts On Lisp And Racket (2019)
&gt; I have met a lot of people who said that they could do things with Lisp 20, 30 years ago that languages either cannot do today, or could only do recently.<p>&gt; It looks to me like the Lisp community knows something the rest of the world does not. They are not searching for the next hot thing. They seem to understand things on a deeper level than other communities. Perhaps “enlightenment” is not an overwrought term to use.<p>For those that haven&#x27;t read this before.  For me, any article making claims like this simply brings to mind the Lisp Curse:<p><a href="http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210617140457&#x2F;http:&#x2F;&#x2F;www.winestockwebdesign.com&#x2F;Essays&#x2F;Lisp_Curse.html" rel="nofollow">http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210617140457&#x2F;http:&#x2F;&#x2F;www.winesto...</a><p>(Not currently available...  Last snapshot is from June, so unsure whether this is permanent or just temporary.)<p>Lisp is extremely flexible as a language.  The core is very small, especially if you look at something like Scheme.  But it lets you easily create and extend the language into what practically becomes a domain-specific language (DSL) for whatever problem you&#x27;re working on.<p>Except what this really does is push things from being <i>technical</i> issues to being <i>social</i> issues.  Sure, maybe I know Lisp.  But how long is it going to take me to learn what your ultra-customized, macro-laden particular flavor of Lisp?  And one has to do that for every single new project requiring coordination...<p>Lisp is not one language, but a wide variety of personal languages that happen to share a common core and syntax.