> I consider .NET to be an ecosystem including all tools, projects, platforms, organizations, and groups of developers.
Well, that explains the otherwise baffling statement "I left .Net because ... git is so much better than TFS"
That is an opinion that I also hold, but isn't relevant.
If the conclusion is that "but .Net comes with a mindset of using all and only the MS tools" then yeah, avoid narrow-minded people. Again, is that relevant?
Yeah, I don't see this problem. Maybe I'm just an outlier, but when I was a .NET developer, I would use non-MS tools all the time. Git is better than TFS, just as nUnit is better than MSTest. TeamCity is better than TFS. Visual Studio with ReSharper is better than Visual Studio without.
Good technologists will use a heterogeneous toolkit no matter what ecosystem they're working in.
The trouble is that "the ordained path" is MS tooling all the way. I suppose there's a lot of pressure on MS to provide a prescribed method and they're satisfying a market demand, but when I worked in .NET I had to make very deliberate choices about avoiding MS tooling and keeping it pinned back into a corner of my project. If left unchecked, it would try to dominate by default.
> The trouble is that "the ordained path" is MS tooling all the way
Every .Net shop that I've walked into, "the ordained path", speaking about the coding culture, was nUnit, TeamCity, Resharper, svn (later git) etc. Maybe you worked at the wrong places.
My anecdote doesn't trump your anecdote, but the reverse is also true.
Well, that explains the otherwise baffling statement "I left .Net because ... git is so much better than TFS"
That is an opinion that I also hold, but isn't relevant.
If the conclusion is that "but .Net comes with a mindset of using all and only the MS tools" then yeah, avoid narrow-minded people. Again, is that relevant?