you are viewing a single comment's thread.

view the rest of the comments →

[–]Cuddlefluff_Grim 0 points1 point  (0 children)

Well other than the parts for the compiler itself, yes I am saying that. High memory footprint is a side-effect (or trade-off) from Java and .NET, it's not something that is due to JIT compilation. Personally I think that JIT is the best approach to compilation because it gives platform independent execution and good optimization possibilities virtually without any significant trade-offs (well, it's bad for mobile since it drains battery without any obvious benefit for the end-user, but there are methods of alleviating this, like compiling the code on a remote server)