About LISP

I started playing around with some LISP because you faggots never stop talking about its greatness and I'm truly amazed. At how shitty it really is.

A simple loop printing "hello world" eats up 40MB of RAM. And if you start up 10 of them it takes up 400MB. What the fuck?

No wonder no one uses this garbage.

>>30
Besides that, PROFILE comes with its own overhead
My version doesn't. See "CALCULATE OVERHEAD"???

That's not cons cells. It's bytes allocated you retard.
Angels on a pinhead, ad hominem,

Haha, shows you don't even know the language if you type that in.
straw man argument,
FORMAT is incredibly complex, yet it's so well optimized that it only had to alloc ~400 bytes to print that string.
Yeah, it had only ~380 unecessary bytes allocated. We should be glad it didn't blow up as well? Also, like you said it's incredibly complex but misbehaves on something simple, I wonder how it'd do for complex input... CRAP!

Just like you manually malloc and free your strings.
I don't. Take a look at this code and LEARN what means to be fast

#include <stdio.h>
int main(void)
{ char s[] = "OP is a faggot"; unsigned int i = 0; while(i++ < 100000) sprintf(s, "%s", s); return 0; }
Bytes allocated: 14 bytes for the string, 4 bytes for int and another 4 for the return value (int). I was right: lisp sucks.