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.
In theory, ruby and python could also be compiled, it just isn't implemented that way. But, compiling weakly typed languages is unlikely to give a big performance boost and could even hurt it a bit by making large code (if the compiler was not good). If compilers were much smarter though, perhaps python and ruby would be able to be compiled and get a signifigant performance boost. 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). The main reason is that Ruby is not > very good optimized -- AFAIK during most of the history of Ruby, > running performance was not one of the main objectives. Recently I > overheard that this changes these days. > > Python has much the same problem (not too much effort in high > performance interpreters as compared for example to Java or C#). > > -- > Until the next mail..., > Stefan. > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ >
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
