Can you give reasons why you wouldn't use it in 2018? Also, what is your proposed alternative? It's disingenuous to dissent without offering the people the savior. If I own a company, need a large swath of developers and we'll assume any random product that could consist of mobile/native app/games, you name it, I'm going with C# everytime because there's nothing else like it. I'm not committing 100KLOC+ of code in some random version of Python, that like all code, may live a lot longer than anyone ever expected. That's for sure.

It's one of very few fullstack solutions available for game (serverside+Unity), mobile (serverside+Xamarin) and web (serverside+Blazor), maybe you want a WPF or UWP app too. Or all of it for a single stack shop for anything you want. Nothing else is pulling all of that off today, and may never. MS is doing a fantastic job keeping it vibrant, alive and supported. You're not really convincing me without more than what you left there. A few years ago, yes, I would've agreed 100% with the general attitude but the tide has turned. I dove in deep on Python, got back out before I hitched my career to that.

To specifically address the points I disagree with.

-Tooling falling off? Examples? I've worked around or with it for a decade now and never saw the tooling fall off.. it's best in class. I really don't understand how this is any worse than anything else.

-Build toolchain? An example of a dire toolchain is Javascript's, not C#'s. That is a mess that I want nothing to do with. I can't get behind this one either.

-Roadmap schizophrenia? They have it figured out now on the .Net Standard and Core. Your alternative is Python 2 to 3 transitions. That was the real mess.

-Integration with other Microsoft products? Good or bad, you probably aren't going to find better integration with MS products than using .Net. I can't get behind this complaint either.

That said if anyone has attacks on .Net I'm willing to listen but I don't see it. It's the worst, except for all the others.