Kotlin might fit the Java niche, if you trust someone that sells IDEs to make a language.
Go's niche includes being native. If you discard that, then virtually anything that is "easy" could fit it.
Go's niche includes being native. If you discard that, then virtually anything that is "easy" could fit it.
While one can excuse themselves that they were commercial, GraalVM native image, and OpenJ9 offer free beer alternatives.
However, PTC and Aicas are still in business,
https://www.ptc.com/en/products/developer-tools/perc
https://www.aicas.com/wp/products-services/jamaicavm/
IBM's commercial one is now freely available on OpenJ9,
https://www.eclipse.org/openj9/docs/xaot/
Finally, if you are using a modern Android phone, an AOT compiler is in the box since Android 5, and it was modified into a mixed JIT with AOT compilation on rest since Android 7.
GraalVM happens to be the evolution of MaximeVM, and certainly not the only game in town.
Or is the niche not being able to understand JVM languages, that expect developers to have PhD skill levels, as per Rob Pike's own words?
They would at least know how to make a language that's not a pain in the ass to analyse, which is probably in its favour.
I see you've yet to meet Scala.
> they're not tied to one particular IDE since LSP took off.
There's at least one language server for Kotlin.
I'm not even a interested in (let alone a user of) Kotlin, but you seem to have a very not-objective view of it for some reason.
> There's at least one language server for Kotlin.
I didn't say there is none, I said that any modern language has one. An IDE is not a selling point anymore, in my humble opinion.
> you seem to have a very not-objective view of it for some reason
I just think that shoehorning Kotlin into "the go niche" is absurd , and that the "good code analysis" argument is moot.
That's what you say, but you don't really tell us why.
You're the one asserting that it's unsuitable. So it very much is.
> If you think something like compiling kotlin instead of running a JVM is akin to compiling with go tooling, then at this point anything that somehow compiles to native (and beyond) is in the "go niche".
I don't know about the other commenters, but that's literally the only criteria you've deigned offer so far, aside from some sort of conspiratorial implications.
Look, this is getting ridiculous. Go offers easy+fast tooling out of the box. Any JVM language, compiled or not, will never be anywhere NEAR go's tooling in those terms. The extra compilation layer just makes it actually much worse.
And I don't even find go particularly appealing.