The "Why I hate Common Lisp" Thread

I'll go first.

SHITTY SOCKET LIBRARIES

Clisps socket libraries are nice.

its gay

They're just simple wrappers around C/C++ libs.

>>4
I'm ok with this.

no standard for threading, poor to nonexistent threading support
interpreter can't be loaded as a library in c
asdf-install (every single thing about it)
unchecked/undocumented conditions
have to code in emacs
compiled binaries are too large to distribute
for every mandatory feature of a software platform, there is one implementation that has it.  these are not the same implementation.
horrible syntax (parentheses (nesting (15 layers (to do the simplest thing (required (also algorithms (must be inside out (unreadable)))))))))))))))))))))))))))))))))))))

>>6
(also algorithms (must be inside out
(if b (f (g 1)) 0)

if (b) return f(g(1)); else return 3;

>>6
Only gay languages need hardware-abstraction shit like threading

))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))

(p(a(r(e(n(t(h(e(s(i(s)))))))))))

(make-thread (hate common-lisp (reason?)))

1) There are two namespaces.
2) )))))))))))))))))))))))))))))))))))))))))))
   automatical ')' insertion with python style indention would be nice.

Functional languages are for mathematicians, not programmers.

No modern, real world applications have been written in any derivative of Lisp.

/thread

>>12
>>automatical ')' insertion with python style indention would be nice.

I've thought about that. I was trying to think of a way to do it to scheme, but then I couldn't figure out how to differentiate between:

(cool-function-that-returns-a-function)

and

((cool-function-that-returns-a-function))

using indentation. I guess the parans for functions calls could stay while built in syntax structures like let could somehow take advantage of indentation in a predictable way.

>>13
You're right to hate lisp, but for the wrong reasons.

>>12
You mean SRFI-49?

>>6
asdf-install sucks, yes.
But that's why you use [b] QUICKLISP! [/b]

>>17
: (.
O k a y  I ' l l  l e a v e  n o w .

>>17
asdf-install is a bit unportable, I just manually set up ASDF.
The main problem with CL is probably the setup time and large binaries (unless you use ECL), but I don't find either of those bothersome. There's also some minor problems, but if you know CL, it's easy enough to hack the implementation or write your own code that fixes whatever bothers you. These are problems with most languages which aren't too popular, but popular enough to get a lot of good code written for them.

>>19
but if you know CL, it's easy enough to hack the implementation or write your own code that fixes whatever bothers you.

BULLSHIT

>>20
Maybe for you, but I've hacked at SBCL, ClozureCL and quite a few libraries and tools(such as SLIME) without having to spend too much effort to accomplish what I needed.

The 'why I am dumb' thread.