3 ms·

> In the .Net world, if MS released a certain library, that would become the de facto choice for nearly everyone in the ecosystem. Competing with the MS options

> In the .Net world, if MS released a certain library, that would become the de facto choice for nearly everyone in the ecosystem. Competing with the MS options was almost impossible. While I get your point, I personally prefer it this way. Whatever Microsoft will put out will at least be “ok”, regularly bug fixed and supported for ever and ever. I prefer to having an ok default and just rolling with it.

DeathArrow 5y ago
And having a default library for everything is great since you don't have to learn countless libraries doing the same thing and you can understand code written by others with ease. But this is a tacit agreement in the .NET world. It's not only about libraries written by Microsoft. When sensible libraries such as Automapper or Newtonsoft JSON appear, everybody defaults to them.
- hackerfromthefu 5y ago
  And there are alternatives. But the core libraries are a safer bet for long term maintainability, and they get invested into to survive long term. A big thing that people often don't understand about .NET is it has the perspective of being all things to all people. One example of this is that it gives first class support for supporting living extensible systems for long durations like decades which is often not really the case for other stacks. Hence the prevalence for approved long term supported libraries typically with first party backing from MS. Another aspect of this all things to all people is that it has lower level closer to the metal performance features that people only used to high level stacks often mention they don't see the need for (although they don't say it like that!). Another aspect is you can do pretty much any kind of application in it, from web to native to high performance games or latency sensitive systems (with some special techniques) to well almost anything. The ability to access low level performance while still having high level general ergonomic APIs is critical to this.

DeathArrow 5y ago

And having a default library for everything is great since you don't have to learn countless libraries doing the same thing and you can understand code written by others with ease. But this is a tacit agreement in the .NET world. It's not only about libraries written by Microsoft. When sensible libraries such as Automapper or Newtonsoft JSON appear, everybody defaults to them.

hackerfromthefu 5y ago
And there are alternatives. But the core libraries are a safer bet for long term maintainability, and they get invested into to survive long term. A big thing that people often don't understand about .NET is it has the perspective of being all things to all people. One example of this is that it gives first class support for supporting living extensible systems for long durations like decades which is often not really the case for other stacks. Hence the prevalence for approved long term supported libraries typically with first party backing from MS. Another aspect of this all things to all people is that it has lower level closer to the metal performance features that people only used to high level stacks often mention they don't see the need for (although they don't say it like that!). Another aspect is you can do pretty much any kind of application in it, from web to native to high performance games or latency sensitive systems (with some special techniques) to well almost anything. The ability to access low level performance while still having high level general ergonomic APIs is critical to this.