I'm torn in how to respond. As usual, I think the answer is "it depends".<p>A few years ago, i got bored/frustrated with using SAS for really specific custom built work/research that also worked at large scales and went searching for a replacement. For my uses, I wanted it to be:<p>Compiled, fast but also flexible, free, have functions, macros, and an object system. (and I wanted to learn something from it even if i ended up not using it).<p>I settled on Common Lisp. The rest of the world seems to be python/R these days. I really do like common lisp, lisp is easily my favorite language so far, but there are some realities which, two years on or so, which i feel able and qualified to share:<p>Some observations on Common Lisp:<p>Cons:<p>-its a big language. I still feel like i don't get all of it, but that doesn't necessarily matter.<p>-its not batteries included. That means you're basically going to be coding ALOT yourself. And that requires a lot of work/knowledge about what you're doing. And if you don't understand good data structures/compsci fundamentals, you aren't going to beat the implementations that already exist in other languages. I want to dismiss this because I'm generally trying to write new stuff that doesn't exist anyway and I want low/high level access simultaneously for performance reasons, but it seems there's always supporting libraries/infrastructure underlying some of your work that you didn't really think of that don't exist sufficiently now. THIS IS REALLY THE BIG NUMBER 1 STRIKE AGAINST THE LANGUAGE. Do not underestimate how much you'll be doing if you think you can just implement techniques that have already had X years of work being implemented in other languages.<p>-It is not dominant, or even widely known any more. Workmates/friends will ignore you for writing in it. Your work probably won't let you use/install it...<p>-You'll resent other languages if you successfully learn it.<p>Pros:<p>-of course, i find current libraries in languages don't do what i want, so i often find i have to rewrite things anyway.<p>- Its great for solo, exploratory work or work that doesn't exist yet.<p>- Its fun/liberating to code in.<p>- It will beat the absolute pants off of Python/R performance wise if you ever get it up and running and if that's important to you. It is to me. But you can only implement said performance if you know what you're doing.<p>- SBCL kind of gives you the best of both the dynamic/static compiled/interpreted worlds.<p>- I found it really does open up your eyes to a lot of compsci-theory aspects other things gloss over. Of course, by glossing those aspects over, python/R can make your job a whole lot easier if they aren't important...<p>Python is actually pretty cool, but its also pretty slow. I really do prefer lisp, but most of the world prefers algol-esque syntax. I think its really up and coming in the machine learning/stats world.<p>R: Is liberating coming from SAS. Has huge stats community backing and huge number of stats packages. Coming from LISP however, its the horribly disfigured plastic-surgery older-hollywood nightmare of a beautiful starlet you remember from your youth, but has now carved up its face to try to look like the other young starlets :P (haha, only serious). Which is to say, its got enough lisp influence behind it to seem familiar, but its a horribly designed/implemented language coming from a programmer background...<p>More accurately though, if Python is slow, then R is SLOOOOOOOOOOOOOOOOOW. Really, its painful to type things at the R repl after coming from common lisp. It has a bit of a cult-like following amongst stats people though...<p>Hope i've offered at least a little bit of valued feedback...YMMV