3 ms·
That's a fair issue, but also a particular use-case. Java seems to be suitable for long running apps where that 100+ms start up time is easily covered as an amm
by Jtsummers 13y ago
That's a fair issue, but also a particular use-case. Java seems to be suitable for long running apps where that 100+ms start up time is easily covered as an ammortized cost over the apps uptime. It still doesn't answer what benefit would Java have if it had been native compilation from the start versus VM (and later VM with JIT-compilation). It would not have been able to run on near the number of platforms that it initially supported if, instead of porting a VM, they'd had to support many OS/ISA pairs. The VM -> VM w/ JIT approach provided a deployment path based on incremental improvements. Initially support dozens of platforms with good enough performance, then over time improve performance on each platform. Versus initially support a handful of platforms with good performance and spend years getting the breadth of platform support.
- pjmlp 13y agoSo what? This was the initial way Pascal and Modula-2 were developed. P-Code and M-Code were their bytecodes. This didn't prevent most compiler vendors to introduce native compilers and use those bytecode implementations mainly for bootstraping purposes. Writing compilers is not that dark magic thing many think about. Well, except when targeting x86 processors, maybe. :)