Still Mono, Xamarin and Unity preceded that decision.
True, but even now the C# library ecosystem is lacking compared to e.g. JVM/JavaScript/Python ecosystems. And that's definitely because it was historically closed source and mostly (but not entirely) single-platform.
Re:Swift Algorithms
by JamesSwift on Thursday October 08, 2020 @09:44AM
(#24719034)
I dont agree with "C# library ecosystem is lacking". The nuget ecosystem is massive, and the paid offerings side is much larger (owing to more of an enterprise audience generally). There arent a lot of well known projects that _run_ on the CLR like there are on the JVM, but the in-language ecosystem is just as robust as those other ecosystems if not more so.
> the paid offerings side is much larger
The fact that a lot of the offerings are paid is a massive negative to me. I don't know of any other language ecosystem that is like this.
.NET CLR + BCL was originally released as BSD code, Rotor project, but no one cared about it.
.NET was also available in other platforms where Microsoft saw commercial value, via partner agreements.
I think C# had that problem for a long time, but Microsoft did a great job / made a great strategic decision with .NET Core I think.