Other languages tout fast build times (that actually are not that fast) completely unaware they are stuck in slow feedback loops.
Wait until you deal with slow loading process that is independant of your language. (ie even infinitly fast build time wont' save you). Once that data is loaded into your data structure you want it to STAY there. Lisp wills save your butt allowing you to continue to develop with the tight feedback loop.
JS + devtools...
A dialect Scheme was used in the famous MIT lecture course [2], the video [3] and book[4].
Many computer scientist grew up with thinking in LISP.
[1] https://queue.acm.org/detail.cfm?id=1039523
"So the problem is—I’ve said this about both Smalltalk and Lisp—they tend to eat their young. What I mean is that both Lisp and Smalltalk are really fabulous vehicles, because they have a meta-system. They have so many ways of dealing with problems that the early-binding languages don’t have, that it’s very, very difficult for people who like Lisp or Smalltalk to imagine anything else." -Alan Kay
[2] https://en.wikipedia.org/wiki/Structure_and_Interpretation_o...
[3] https://ocw.mit.edu/courses/6-001-structure-and-interpretati...
Well, okay, to be fair the real reason is probably because Common Lisp is very mature, well specified, has a lot of useful libraries (Quicklisp is great), and several implementations can produce very efficient and fast code (about as fast as GC code can be, especially if you make good use of facilities like dynamic-extent).
Also the sense of tradition can be appealing - it is the second-oldest language still in use, after FORTRAN, and has been incredibly formative in many respects. It‘s similar to how learning Latin doesn’t only allow you to read a lot of great works of the past, but also helps you understand modern languages.
Partially as a result of all this, Lisp has other things that Haskell lacks, such as good editor support and a great REPL. Haskell editor tooling is awful and although it has a REPL it’s nowhere near as good as Common Lisp’s.
I'm looking forward to a replacement; Unison might be it, a lot of its choices are better oriented towards interactive development, but the jury is still out on this. Other candidates imo are lean, agda, roc, verse (this one I heavily doubt), or ghc fixing itself so this discussion is unnecessary. But there is space for a language that cuts out the historical baggage. For a while, I hoped that would be purescript, but I think that unlikely at this point.
It's just different. I love haskell, but also love lisp. For very different reasons, but they're both delightful expressions of thought.