> Lisp, which seems to go to great lengths to isolate you from the details of machine organization.
Right there, along with Haskell is exactly why Lisp was never an option for me. And much like the author, I've been subjected to the darn thing multiple times since an early age (the 80's).
[EDIT]: and most notably missing from the list: The Lisp ecosystem is pretty much impossible to understand.
There are so many flavors of the darn thing none of which are interoperable with the others.
Every time I found something written in some random dialect of Lisp, there's always a missing piece to get it to run on my machines unless it's a 20 line coding exercise.
I've also never found a list that explains why "this Lisp is different from that Lisp because ..." .
Everyone in that world seems to assume their favorite patois is the best thing since sliced cheese.
Seen from the outside, it's a giant mess.
Makes it impossible to pick the right tool for the job.
Part of the problem is that most anything that uses S-expressions is called a Lisp. And there are dozens of these languages.
You see a headline “Did amazing thing using Lisp!!” and find that it’s actually more “Did amazing thing with A Lisp”, and, typically, not the Lisp you like to use.
Nobody calls C, Java, C#, C++, Pascal, D, etc. an “Algol” or whatever generic term might apply to this family of languages. “DOOM is written in Algol”. But this happens all the time with Lisps.
There's the Common Lisp standard with the Quicklisp library manager being almost fully compatible with SBCL, ECL, Clisp... (the performance will vary a lot, tho), and then there's Scheme, the LISP cousin.
For programming, the best env for CL it's Emacs and Slime, and for Scheme there's Emacs and Geiser. For further programming, Org-babel from Org-Mode wth the accompanying modules for Slime/Geiser with ob-scheme or ob-lisp.
Emacs with Org-Babel it's like having an anotated REPL with options to put anotated marks, graphics and/or export it to ODF or PDF.
Kinda like the Python/Jupyter notebooks but with superpowers.
I feel the exact same way about Python, and Javascript and everyone seems to use and sometimes even likes those giant messes so we can assume for sure that giant messes aren't really the problem here.
Right there, along with Haskell is exactly why Lisp was never an option for me. And much like the author, I've been subjected to the darn thing multiple times since an early age (the 80's).
[EDIT]: and most notably missing from the list: The Lisp ecosystem is pretty much impossible to understand.
There are so many flavors of the darn thing none of which are interoperable with the others.
Every time I found something written in some random dialect of Lisp, there's always a missing piece to get it to run on my machines unless it's a 20 line coding exercise.
I've also never found a list that explains why "this Lisp is different from that Lisp because ..." .
Everyone in that world seems to assume their favorite patois is the best thing since sliced cheese.
Seen from the outside, it's a giant mess.
Makes it impossible to pick the right tool for the job.