Hacker News Reader

No - go Java. ORMs, document generation, reporting, integration, architecture, deployment, tooling, devops stuff. Literally everything is ready to roll out of the box for $0. And it all works.

C# - half of this is available for a fee and the rest is available for a larger fee. And none of it works particularly well. And if anything breaks it's $200 a go to get it fixed.

View on HN

I would go Java if the syntax weren't so stale. C# has continued to improve over the years. The BCL and compiler teams are not afraid of breaking changes between major versions. Stability is good (which is why non-nullable reference types won't make the cut), but stagnation kills the ecosystem and drives new contributors away.

Java syntax is usually pretty irrelevant when it comes to actually solving problems.

C# is a minefield for issues. Linq memory ballooning, null refs, O(WTF) LINQ expressions, tri-state logic caused by nullables, spinlocks from hell (ReaderWriterLockSlim), missing symbols and more sourceless black boxes than anything. Oh and three different subtly broken XML APIs.

More language features don't make it better.

Reply on news.ycombinator.com