which of course is also a major weakness of SQL.
There is a deep philosophical issue here.
If I write a Java VM in C why can I write a program in Java that can run
faster that a functionally equivalent program in C? (or assembler for
that matter).
Is there a permathread for this?
The implication is that Java can create a sequence of instructions that
C can't.
Rick
Elliotte Harold wrote:
> Tei wrote:
>
>> If you really need raw speed C or C++ will be always faster than Java.
>
> No, it won't. It has been proved false by counterexample that C/C++
> will *always* be faster than Java. On some problems, Java already is
> faster than C or C++. Fact is some problems are more amenable to the
> sort of runtime JIT optimization Java does. Others are more amenable
> to the sort of static optimization C/C++ do. Which one is faster
> depends on what sort of problem you have.
>
