lisp is 1-2 times slower than c, a pretty good result and significantly better than java which is like 10 times slower
Name:
Anonymous2013-03-05 13:15
Better tell me, why Lisp uses these retarded symbols, instead of using something like fixword (akin to fixnum) to hold strings? Because 64-bit register can hold 12-char string - that is any english or chinese word.
Name:
Anonymous2013-03-05 13:20
>>4
I do imagine that languages like Lua or JS should execute much faster, because with perfect hashing method call would be just modulo vtable access and single comparison.
I would say it's easier to optimise Lisp code than it is to optimise Java code. If you're taking benchmarks and comparing them, then note that you're comparing IMPLEMENTATIONS of languages.
Name:
Anonymous2013-03-06 11:29
>>8
I recall they banned some Lisp code, because it used macros, which is considered cheating.
Name:
Anonymous2013-03-06 11:32
Functional code is intuitively more inclined to optimisation than braindead "do this then this then this, oh and anything you do might have side effects" imperative code. The opposite is only true since more effort has been put into imperative language compilers because they are more popular because imperative programming it is easier to grasp for most (i.e. simple-minded) people than functional programming. The Von Neumann model of computing should never have survived past assembly language, or at most up to the point where they managed to bootstrap C successfully.
>>12 (declare (optimize (speed 3) (safety 0) (space 0) (debug 0)
CFLAGS JUST KICKED IN, YO!
Name:
Anonymous2013-03-06 12:19
>>11
except our brains don't work that way. at least mine doesn't
Name:
Anonymous2013-03-06 12:28
>>15
You sound comfortable in your limited paradigm. Perhaps you should try something else before resigning to “well I just work that way is all”. I find writing imperative code now feels like I am a child trying to write an essay on an etch-a-sketch with my hands taped together.
Why do we need Java, when every PC runs x86? Just use some sandboxed executables.
Name:
Anonymous2013-03-06 16:22
>>17
Not >>16, but ... Would you say learning one language from each paradigm is the best?
I think it's a pretty good idea to learn to use at least the imperative, functional, and logic programming paradigms. You can still write practical code using only one of those paradigms, but I suppose it gives you different ways to think about problems.