Thinking in Lisp

SQL, Lisp, and Haskell are the only programming languages that I've seen where one spends more time thinking than typing.
That's because it takes forever to think of the solution in Lisp and Haskell as opposed to a decent language. Faggot lispers will spend most of their time figuring out how best to abuse recursion because they think it makes them leet programmers or some shit.

>>1
Nope. It's much easier for me to write Lisp code than Java or most other languages. Once I mostly know what I want to write, I just write it. With other more popular high-level languages, I tend to write masturbatory AbstractFactoryFactories filler instead of just writing what I want, because the language forces me to fit my idea to their way of thinking, instead of allowing me to express the idea as directly and as clearly as possible.

Faggot lispers will spend most of their time figuring out how best to abuse recursion because they think it makes them leet programmers or some shit.
Don't confuse Lisp with Scheme. Sure you can abuse TCO all day long, but most of the time I write in CL, which has decent looping constructs (doesn't mean I don't prefer to write in a declarative manner where possible, but I'm not going to go out of my way to write in a functional manner if what I want is better acomplished some otherway), I don't go out of my way to use TCO.