.NET Core has been a bittersweet experience. At one angle the ideals behind .NET Core are fantastic and it will open up C# to become ubiquitous like Java. On th

.NET Core has been a bittersweet experience. At one angle the ideals behind .NET Core are fantastic and it will open up C# to become ubiquitous like Java. On the other hand, their development process makes me want to throw it back at Microsoft. Developers were allowed to head up into their ivory towers. Even to this day they're coming up with ways to explain how the "tooling" is still beta or broken. The .NET Core developers obviously just cared about the fun internal stuff and left us to handle the ugly, real world stuff ourselves. If they cared, they would have built tooling alongside the framework. It has been almost six months since the .NET Core release and we still don't have the "proper" tooling. They haven't done SignalR either. I've never been held in limbo for so long. The only reason I'm hanging on is because of C# and Visual Studio. I don't even know what the significance of the ".NET Core 2.0" or ".NET Standard 2.0" releases are anymore, the amount of complexity added to the development decision making process in .NET Core got out of hand many months ago. I'm not the only serious .NET developer who is feeling puzzled about the purpose of all this. Sure, it was an interesting idea, but man the execution could have been better.