3 ms·
The title implies that it's comparing the runtime engines, and the performance is absolutely a major selling point of any such comparison, even if the practical
by jcranmer 11y ago
The title implies that it's comparing the runtime engines, and the performance is absolutely a major selling point of any such comparison, even if the practical effect of any difference is negligible. Ultimately, the comparison claims to be between the CLR and the JVM while it's more like between C# and Java, given how it only covers fairly superficial features at the front-end level and not what can and can't be done in VM code, let alone how different VM architectures can have major impacts on code design, etc.
- bunderbunder 11y agoI think the reason for this particular list is that it's from the standpoint of a programming language implementation team, and one that's currently working on targeting a 2nd platform. Given that, it reads as a list of what the VM can do for you and what you'll need to do yourself in the compiler.