Hacker News new | ask | show | jobs
by _halgari 2753 days ago
Why compile ahead of time when you know nothing about what the target platform is capable of? Why compile before profiling to make sure you run the correct optimizations? Startup times are sometimes important, but it's not the end-all-be-all of computer science.
1 comments

It's not about startup times, just in time compiled code is slow in reality, and no contrived cases, of which there have been many, will change that. There is no profiling in just in time compilation. In order for a JVM to pull that off, it would first have to just in time generate code with counters, run that code, figure out when to analyse the results, then recompile and re-order it. That entire provess would make it run even slower than if it were interpreted.

Better then to do that once and generate optimized, reordered machine code and put the pedal to the metal during the lifetime of the program's run. Except there is no advanced optimizing compiler for programs which utilize a JVM, gee I wonder why... heh heh!