I appreciate the effort in .Net Core, I think the info-marketing side could use some attention and with 2.0 some redress to the CTO types... for now, despite some adoption, it's not exactly proven out.
I will say that for a few of my early tests, it does about 60% more work than the node based app I ran against... though that was still more effort than I liked, and took a bit longer to write than the node version, either of which frankly exceeded the throughput requirements and could scale horizontally.
I'm looking forward to seeing what comes of things... I miss a lot of the integrations that C# + VS offered, but don't miss the lag that is so present in my mind even today regarding working in VS. I do love VS Code though, and haven't tried VS2017 so can't comment.
You've run every single example in the .NET Core documentation? Or you like opining about things you have no experience with?
Have you? Do you have an example of something that doesn't? Or are you talking about something you have no experience with?
Every single example in the .NET Core documentation compiles and runs, please stop spreading FUD.
Version 1.2 with the release of VS 2017 now has all the appropriate tooling to make everything work well. The whole project is less than 2 years old and by the end of the year we'll have .NET Standard 2.0 with most of the APIs back, almost full compatibility and even better tooling.