There is also Pdm now I recently learned, which is supposed to be a more modern alternative. As an alternative to poetry that is; pipenv is yesterday’s solution.
That is actually a nice analogy! No one, not even the pro formula-1 drivers will want to drive a f1 car in regular traffic. Much the same with these languages (apls, lisps, forth, etc); they have their place and role, but is better not used in regular open source or commercial codes.
I was holding my old iPhone3 in my hands a few days ago (one of my kids have collected a few phones in the house over the years). It felt so good, light and small. I really long for a phone in that form-factor again, the big phones of today is just silly.
My guess it's a proportionally low number. I looked into matlisp when I did my PhD in scientific computing - none of the other people I worked with had any interest in it. I couldn't pursue it since I would have to reimplement or interface each and every library myself, a workload I couldn't justify at the time.
So, although lisp might have been great, in the end I stayed with Python/C++. Guess I'm not the only one with similar experiences.
There are still days when I miss fvwm. Not because it was that great, but because I used it for so long that my fingers still remember the keyboard shortcuts I configured. But I moved to OSX and just had to adapt. I guess moving on isn't always the most important thing, but stay productive. If that mean staying with some old software I'm all for it.
Maybe to mainstream to make the cut!?