2 ms·

I really like C#, and I would generally vastly prefer it to NodeJS on the backend. I think one weakness is the library ecosystem, the competitors are stronger t

I really like C#, and I would generally vastly prefer it to NodeJS on the backend. I think one weakness is the library ecosystem, the competitors are stronger there. Most of the time this doesn't bother me as I also tend towards limiting dependencies in general. There is a positive aspect to this, as it makes decisions easier as well. For many areas there is often a single good choice, there aren't dozens of web frameworks you have to evaluate. There's ASP.NET Core and then nothing else for a long time. And for the most part those are pretty good, so it does not feel limiting. And C# doesn't have to be too enterprisy and over-abstracted. The community does tend a bit too much towards unnecessary abstractions in my opinion, but you don't have to use it that way.

lloydatkinson 1y ago
> I think one weakness is the library ecosystem, the competitors are stronger there. People say this but is it really the case? Look how much NPM has been attacked by malware recently, and all because people are indirectly installing simple colour libraries that are 20 layers deep of dependencies of dependencies. Then you get the fucking stupid stuff like `is-odd`.
- StrangeWill 1y ago
  Long-time C# Dev here -- yeah I'm still jealous of being able to find more esoteric libraries in Node, Python or PHP -- or just having more options then someone's back-yard half-baked implementation sometimes. On the other hand, I have nearly 20 languages under my belt and have been writing code professionally for 22 years -- I still use C# most of the time for a lot of other reasons, just this is one of the bigger pain points.