I don't see how that's any better than JRE + JDK. Runtime environment + development kit, with the ubiquitous J- prefix. I remember terrible confusion in the bl

I don't see how that's any better than JRE + JDK. Runtime environment + development kit, with the ubiquitous J- prefix. I remember terrible confusion in the blog comments back when they first announced .NET Core. It was not helped by the fact, that, for example, you can build ASP.NET Core applications to target either the .NET Core runtime, or the "classic" .NET. You can build libraries to target "classic" .NET, .NET Standard, or .NET Core. I'd say the situation is worse than in Java world. It'll probably resolve itself though once they merge everything into a single framework.