Maven is already able to compile a the code with Java 6/Java 8 and the module-info with Java 9. With jlink, you can then create your own jdk and AOT the part of the code you want with jaotc.
Maybe those tools are too new and the perf are not great ?
JEP 295 says: "AOT compilation must be executed on the same system or a system with the same configuration on which AOT code will be used by Java application."
There is also a compiler for Kotlin that builds native binaries instead of JVM bytecode. It is a different project from the same company.
I'm sure someone will be happy to correct anything I got wrong :)
edit: I don't think this will happen to JetBrains. edit2: Forgot the "Delphi" name, but it was basically TP w/ libraries.
I've yet to write any Kotlin in anything other than Vim and Atom though... and Gradle built those apps just fine. So I'm not sure I see a real comparison here.
That said, the IDE plugin can still use some stability work.
Not sure if that is true. Many people are still using vim for many newer languages. I think it depends on the language.
Some languages are simply more IDE-reliant than others. Statically typed languages with a large vocabulary (Java, C#, Scala) tend to benefit more from IDEs than simple, dynamic languages like Python and Ruby.
And there are newer languages like Go. Go was designed to not require an IDE while not being opposed to one.
I think the language server idea is a brilliant one and probably something we'll see more and more of, because it makes a language completely editor/IDE agnostic. It would allow folks using vim or VS code to debug or refactor as cleanly as full-blown IDEs. I suspect this will lead to a decline in the specialized IDE market (Jetbrains).
I remember working with C++ in Visual Studio when that new refactoring plugin became popular (tomatoe something something? later bought by Microsoft) and although the plugin tried its best, it often stopped working with files with a lot of ifdefs and macros.
B removed some features from BCPL that were too expensive to implement. I never understood why they didn't continue that idea in C by applying it to the syntax as well. Wirth knew what he was doing.
https://en.m.wikipedia.org/wiki/Turbo_Pascal
and as far as I remember I never had to leave the IDE. The step-by-step debugger felt like magic.
Maybe it's already this way? I'm really not sure, but I'd appreciate a NetBeans or IntelliJ dev to clarify. It'd be awesome if these changes were done collaboratively.
Many many corner cases are not accounted for, and the way Kotlin is under-spec'd and developed with so many of the IntelliJ libraries, you'll never see any independently developed implementation.
This is not to say the language isn't great, it is. It's only heavy development while focused on lower level aspects that this becomes a constant theme.
Idea developed Kotlin as a better Java. Most of their IDE is now written in it. Deep integration with the IDE was a design goal from day 1.
They release the IDE plugin and compiler with the same version number. They are basically developed together. I usually find out about new Kotlin releases because my IDE prompts me to update the plugin. Happened to me this morning with 1.2.61.
