On 5/1/2013 9:40 PM, S. Dale Morrey wrote: > Depends on if you mean faster 1 time, or faster after running for a time. > > Java has a much higher startup overhead making it unsuitable for programs > that must run quickly and then exit. However JIT will speed up things that > need to be run for long periods of time, including compiling sections of > code that are really frequently used all the way down to the bare metal. My understanding of it (and .NET CLR stuff) was that it was JITed on first run, and then never had to be JITed again. So the first time you ran a Java/.NET app, it had the initial overhead. Subsequent times it does not. Is that not correct? Why would it be modifying it's code in the middle of runtime? Seems gloriously inefficient and overly complex to do it that way, but compilers aren't my favorite thing anyway, so I could use some edumacation.
-Tod Hansmann /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
