Comment by ActorNightly
Comment by ActorNightly 3 days ago
Anything that runs on JVM should not be invested in.
Comment by ActorNightly 3 days ago
Anything that runs on JVM should not be invested in.
Because the idea of classes is baked into JVM. So when writing inline code, with groovy, scala, kotlin, whatever else, the compiler has to basically insert fake classes into the jvm.
This may seem trivial, but because its fundamentally "hacky" its not something that is ever going to be as easy to work with and expand.
Pretty sure everything in the jvm has to be tied to a class structure by definition.
Why? I bet you never even wrote custom VM for your lang/architecture.
There are like dozen of implementations for JVM alone: sun, Oracle, gnu, IBM etc etc