@lxsameer There are a lot of things I like about it. This is a great question, 'cos everyone will have different answers. I have a few, so hopefully I'm not just duplicating them.
I started on it a long time ago, using clisp, but took a long break. But what brought me back was remembering how I could easily talk my way through the code, to describe verbatim what it does. I got into sbcl because it is obviously more refined, but I still use clisp for anything quick I want to accomplish.
People complain about the parenthesis, but doing so ignore all the curly { and same number of () all over their code of choice. I like that Lisp's parens do not get in the way of reading what the code does. Don't listen to anyone complaining about parens, unless their language manages without some sort of equivalent. None of them do. It looks different, but hell, Python looks super weird, overly long and skinny, and everybody loves it.
To me print(something) is disruptive. (print "something") is not. Especially if that print("something"); has that semicolon on the end. wtf is that for? And this increases when "something" should be a function to output whatever that something is. In Lisp, it's pretty slobberproof, and still only takes the one line you started with (unless you WANT to make it pretty ans split it out).
I like that if I don't quite know how to do something, but I know how to start it, I can fudge my way through by writing the function, and the parts I don't know yet are just other functions I haven't written yet. I can then work on those functions after I am done writing the main thought I had. I can even make those uknowns a placeholder providing a fake output if I need to, and then they are right there ready for development once I get to it. Unlike some languages, the functions don't necessarily all become function calls, so eventually it becomes efficient while still being quite readable.
So many things. I simply can't think that way in C. I suppose I could, but all those damn ; are there, and other finicky things that get in the way of creativity when they don't really need to be there. Just a set of () around every separate thing.
Some tags to help with exposure (look upward in the thread if you got here because of one of these tags):
#lisp #commonlisp #scheme #clojure #sbcl #clisp
