Hacker News Reader

Comment by mhh__ | Hacker News Reader

C# is a pretty bad language when you take away the stack it sits atop of. I do mostly like the async but developers put up with a lot of shit to e.g. use the msft networking stack and containers

View on HN

I feel the opposite. It is one of the genuinely competent languages out there, if you're the kind of person that isn't upset about it being a "kitchen sink". Instead, I feel like the ecosystem, community and reputation hold it back. There are nowhere as many useful and popular packages to reach for as Python for example. Unity3D always lags behind in runtime and language version and had amazingly bad package management -- this further hamstrung C#, because the language is never used in a vacuum.

Care to elaborate on what would make C# a bad language?

It's a product of an era of OOP when the idea of a program fitting in a developers head was a dangerous reactionary idea.

They have in fairness fixed a lot of the worst aspects of this by adding basically a second language to it but e.g. I massively prefer writing F# if purely because if I want to do something I can just to it rather than first implementing public static DoThing : IDoThing

  public static DoThing : IDoThing

Yeah... Right.

In other words, C# is a bad language because you don't like it?

What does prevent you from "just do it" in C# without extra classes and interfaces?

The noun to verb ratio is too high. This is a normative statement but it's one I'm willing to make that you apparently can't detect.

Reply on news.ycombinator.com