3 ms·
I don't think it is necessarily about being fair it is just that the philosophy of developers in the .NET world has always been if MS has something then that is
by cc81 7y ago
I don't think it is necessarily about being fair it is just that the philosophy of developers in the .NET world has always been if MS has something then that is the thing we use. I've felt that within Java there are usually more competing products and flavors.
Often the product MS provides is good enough but I remember in the tail end of the web forms disaster there were some good open source MVC libraries inspired by the Java ecosystem but they never really got traction and people kept building things with shitty web forms. This is until MS came with ASP.NET MVC and people started to switch.
I don't think Microsoft wants to kill alternatives. I think they really want a healthy ecosystem to get more developers using .NET but they also want to be able to create a complete developer experience and that sometimes clashes and kills other products due to the culture.
- kevingadd 7y agoThere are definitely cases where the community wins out because it delivers better quality - Newtonsoft.JSON eventually was recommended by MSDN documentation instead of the built-in .NET JSON APIs and the new in-development API is being written by the author of Newtonsoft.
- cc81 7y agoThat is true and that was a pretty big shift and together with embracing open source more, going all in on Azure, supporting Linux etc. there has been changes and that has reflected somewhat in the community as well. I also think people being used to npm in the frontend will make them more likely to start looking around nuget for things that can support their use case better than what exists by Microsoft.
- deleted 7y ago[deleted]