Right now I'm using Lisp for a hobby project. I find it actually really enjoyable. Lisp's metaprogramming support is super powerful. I'm the kind of developer w

Right now I'm using Lisp for a hobby project. I find it actually really enjoyable. Lisp's metaprogramming support is super powerful. I'm the kind of developer who likes to explore different styles of programming. If you're like me, Lisp will not fail you. It really is a "programmable programming language". For example, Lisp is not purely functional, but if you want to force yourself to program in a bit more of a functional style, you can make a macro that disallows the use of 'setf' (Lisp's assignment operator) in a function body, and it's actually quite easy to do that! Maybe Lisp 'failed' because it's too flexible. You can solve your problem in a million different ways. Arguably, that is not a good thing in industry where it is preferred to have a language that enforces a single style on your code base for consistency across developers. However, I'd argue that it is very good thing for a creative individual. You want to have the freedom to do things your way. From what I've experienced so far, Common Lisp offers a unique combination of customize-ability, utility, and interactivity. It's been around long enough for it to have a significant amount of libraries, and it has a multi-threaded REPL (so you can run your main loop and hot-reload your code-updates at the same time, how cool is that?!). As for the parentheses... yes, I can see why Lisp code would be hard to read. On the other hand, with the right editor extensions (parinfer) it's really easy to edit, and you don't even need to think about the parenthesis when doing it. The documentation is alright I'd say, you can find plenty of stuff online. Not sure what else I can say. I'm having a good time with CL... I'll try not turning into a 'smug lisp weenie'?