Merlin Moncure wrote:
On Mon, Sep 15, 2008 at 1:10 PM, Martin Gainty <mgainty@xxxxxxxxxxx> wrote:
accessing:
i *thought* the advantage of creating any SQL procedure/function was the
entity is stored in procedure cache
load time:
Java vs C++ compare here
http://www.idiom.com/~zilla/Computer/javaCbenchmark.html
This is completely off topic as it is, but I can't help it: anyone who
is arguing that Java is faster than C must be oblivious to the fact
that Java internals are *written in C*. If Java was really faster
than C, it would be self hosting, and we would be writing operating
systems, databases, and various other systems level stuff in Java.
(yes, there are a few well known projects, notably lucene, but that's
the exception rather than the rule).
Anybody making the case that Java is faster than C simply doesn't know
how a computer works.
merlin
According to your argument any hardware implementation is limited to
software performance, as it is compiled by a software compiler? In fact,
compiling assembly with a compiler written in C will destroy its
performance to be worse than C? Come on... This is utter bullshit. You
should rather reflect on your last line...
Its worst yet, there are actually situation where the Java optimizer
does a better job than many C compiler. The reverse is also true. If you
are a software guy you SHOULD know that code optimization and algorithm
design are NP problems and have no obvious optimal solutions. It seems
easier to optimize Java code than it is optimizing C code.
Better yet, you should actually read the article. It has the explanation
contained inside it. The domain of application Java has (eventually)
been developed for is just different.
Regards,
- Joris
