2 ms·
In my eyes going native is nice for the distribution of command line apps (if they are static binaries), but also for avoiding the startup time of the jvm. >[.
by tutanchamun 10y ago
In my eyes going native is nice for the distribution of command line apps (if they are static binaries), but also for avoiding the startup time of the jvm.
>[...] but it seems like Go and Rust have already satisfied the desire for modern natively compiled languages
Not for me. Go's type system is too primitive, and Rust is maybe too low level if you don't need the advantages compared to languages with a GC. So a language like Kotlin with a better type system (than go) fits nicely in between the two (that might change if Rust get's a GC type). Especially since it will probably have (or has already?) better tooling considering that Jetbreains is behind it.
- pjmlp 10y ago> but also for avoiding the startup time of the jvm. Funny enough, all commercial JDKs do support AOT compilation to native code, and Oracle is slowly adding support for it as well.