Re: Lisp vs. Perl Round 3: Operator Associativity and Manipulation

And when did Lisp become blindingly fast?

I quote from Lisp as an Alternative to Java

Our results show that Lisp's performance is comparable to or better than C++ in terms of execution speed, with significantly lower variability which translates into reduced project risk. Furthermore, development time is significantly lower and less variable than either C++ or Java. Memory consumption is comparable to Java. Lisp thus presents a viable alternative to Java for dynamic applications where performance is important.

Comment on Re: Lisp vs. Perl Round 3: Operator Associativity and Manipulation

Replies are listed 'Best First'.
Re (tilly) 2: Lisp vs. Perl Round 3: Operator Associativity and Manipulation by tilly (Archbishop) on Jun 09, 2001 at 06:31 UTC
As I have commented before, the general opinion is that Lisp is bloated and slow. This opinion was formed on hardware with 1% of the memory and speed of current PC hardware. Additionally there has beeen a lot of research into how to optimize Lisp. It turns out that Lisp can be optimized very well. If you are willing to give it the right declarations, amazingly so. Most of the ideas that people have for how to make Perl 6 optionally fast? Well Lisp had those ideas ages ago and standardized it into ANSI Common Lisp. And vendors have had years to implement it then fine tune the results...	[reply]

Replies are listed 'Best First'.

Re (tilly) 2: Lisp vs. Perl Round 3: Operator Associativity and Manipulation
by tilly (Archbishop) on Jun 09, 2001 at 06:31 UTC

Additionally there has beeen a lot of research into how to optimize Lisp. It turns out that Lisp can be optimized very well. If you are willing to give it the right declarations, amazingly so. Most of the ideas that people have for how to make Perl 6 optionally fast? Well Lisp had those ideas ages ago and standardized it into ANSI Common Lisp. And vendors have had years to implement it then fine tune the results...

[reply]