[bonesss]

I don't think this issue is unique to MS, but thanks to their historical business markets (Office, small-to-medium businesses), and product portfolio the sense is that many Azure services are spider-webs of related products. That feeling that you can't just use a component in isolation, but that other tightly bound products are often the only way to serve reasonable services.

They've made substantial efforts and improvements, so credit where credit is due. I think the broader .Net community needs to pull their thumbs out and take a hard look at why C# OSS has struggled the way it has, and how the ecosystem should be maturing.

The cross-platform, OSS-friendly, orientation of the F# community has been much more reflective of my technical concerns, platforms, desires, and predelictions.