Julia is a good example for a language with JIT that doesn’t follow the stereotypical OOP layout, so its memory overhead will be only that of the runtime (which

Julia is a good example for a language with JIT that doesn’t follow the stereotypical OOP layout, so its memory overhead will be only that of the runtime (which is definitely not zero, but nor is it too big). > Oh most definitively. On the other side of that same coin, most real life code in JS/Java/C#/PHP/Ruby consume orders of magnitude more resource than their lower level counter parts. Java is actually within the compiled language’s groups’ results with regards to energy efficiency. A good GC can allow to be very power efficient and tradeoff memory for running the CPU — only has to run the GC when it really is close to filling up. After running, it can free the former region in one `nop` by declaring the former region as unused (at least in the moving GC kind).