(no title)
stblack | 2 years ago
In .NET culture, few developers share, fork, or communally develop code, and you sit around waiting for great Microsoft mother to deliver features. There is no ecosystem; there is one provider, and provider is beholden to a couple of guys and, beyond them, investment fund shareholders.
setr|2 years ago
The biggest issue I’ve had is that some of these less popular libraries (both by Microsoft and not) have some truly tasteless APIs, I think mostly stemming from older versions of C#, and for some reason the lowest quality stack overflow answers are much lower for C# than in python — there appears to be much more cruft and outdated information in blogs, stack overflow in C#-land than python. Really in general I feel like python/rust has a higher floor for taste than C#, but at ceiling it’s competitive.
I’m pretty sure though that startup language choice has nothing to do with practical considerations — it’s largely a popularity contest based on hype cycles, and C# is well past its hype-prime.
Nullabillity|2 years ago
This kind of reply reeks of when Phil Haack tried to convince people that (the old) .NET Framework was "open-source friendly" because NuGet existed.
bencyoung|2 years ago
dogma1138|2 years ago
n4r9|2 years ago
* MoreLinq
* Newtonsoft.JSON
* CommandLineParser
* log4net
* UnitsNet
* OsmSharp
* NodaTime
* GMap.Net
* ImageSharp
tompazourek|2 years ago
* Hangfire
* Quartz.NET
* NHibernate
* AutoMapper
* StackExchange.Redis
* the Castle project
* xUnit
* NUnit
* Serilog
* SimpleInjector
These are all very popular long maintained open source libraries I've seen used in many projects.
politelemon|2 years ago
sebazzz|2 years ago
gemstones|2 years ago