Re: Need to recompile a Java Applet as an Executable
On 29-01-2010 17:17, Antoninus Twink wrote:
On 29 Jan 2010 at 21:42, BGB / cr88192 wrote:
anyways, assuming that the browser is not using a poor JVM
implementation (a plain interpreter or similar), Java vs C performance
is not likely to be significant enough to bother worrying about in
this case, and one is instead better off concerning themselves with
writing efficient code (any language will be slow if the programmer
doesn't know what they are doing, and usually the language/compiler is
the first thing to be blamed for the poor performance of badly written
SW).
To be honest, whatever stories people come up with about how good their
JIT compiler is at optimizing on the fly and such like, the truth is
that for many applications, rewriting the bottleneck in C will gain you
an order of magnitude.
I believe the principal two reasons for this are:
1) No overhead in basic data types. AIUI, Java will take many bytes to
store a simple int, just because of all the OO book-keeping that needs
to accompany every single object. Therefore, smaller slices of every
array can fit in cache ---> performance death.
I think we can stop reading here.
Anyone that has read "Java for absolute beginners" know that
int's in Java are not objects and use the exact same number
of bytes as C (on platforms where C int is 4 byte).
If you don't like Java, then by all means avoid coding in it,
reading about it or even think about it.
But why post to usenet about something you have not studied????
Arne