From: Peter Hickman <peter@...>
Date: 2006-07-28T21:36:09+09:00
Subject: Re: For performance, write it in C - Part 2, comparing C, Ruby and Java

That would only get me the elapsed time of the execution which does not 
reflect the actual time taken to run the program. Some higher priority 
task may switch in and suspend the Java program before it completes and 
thus give it a much worse timing. And then you can bet they would be 
pointing this out and saying that the timing were 'utterly irrelevant'.

For most people they have to start up the JVM to run a Java program so I 
cannot in all honesty see this as being 'utterly irrelevant'. Hey the 
executable created from the C source has to be loaded into memory before 
it is run so this means that the timings for the C version are also 
'utterly irrelevant'.

It looks like a troll. It posts like a troll. It is a troll.