3 ms·
Was that true even before `invokedynamic`, which as far as I know was specifically added to make these non-Java languages easier to port and more performant? A
by lxgr 5y ago
Was that true even before `invokedynamic`, which as far as I know was specifically added to make these non-Java languages easier to port and more performant?
All of the examples you‘ve mentioned don‘t seem like trivial ports at least from an outsider‘s point of view.
The JVM itself has definitely adapted to these use cases, but it wasn‘t designed with them in mind.
- kaba0 5y agoYou are right about the reason invokedynamic was added, but as far as I know the JVM always supported dynamic class loading (and thus class creation as well), so while not necessarily in a too performant manner, it could always be used as a runtime for even very dynamic languages. (And I think I left out Groovy which is a quite old dynamic language on the JVM).