On 20/11/2007, Colin Kern <[EMAIL PROTECTED]> wrote: > On Nov 20, 2007 1:56 PM, Nick Apperson <[EMAIL PROTECTED]> wrote: > > > On Nov 20, 2007 12:48 PM, Stefan Nobis <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > "Colin Kern" <[EMAIL PROTECTED]> writes: > > > > > > > I think the reason for Ruby being so much slower is because it is an > > > > interpreted language rather than a compiled language. > > > > > > It's not the main problem (interpreted languages are slower than those > > > compiled to native code, but than even Java and C# are interpreted and > > > don't have such big slowdowns). > > > > Java and C# are both compiled at some point if the same loop is running > > repeatedly. Java is usually compiled "just in time" which is to say as each > > function is first run. I'm not sure how C# is executed, but I think it gets > > compiled before execution. > > > > I just found this looking around for things about Java's speed. Looks > like some useful ways to boost Java's performance. > http://www.cs.cmu.edu/~jch/java/speed.html
It's an interesting page, but it makes certain assumptions about how you're using Java, mainly that you're compiling to Java bytecode. Almost none of this applies, for example, if you're using gcj to generate platform specific binaries via the gcc/g++ backend. cheers stuart _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
