Hacker News new | ask | show | jobs
by metadat 1427 days ago
Coming from Java, Go, and Javascript, C#/.net just plain sucks. Things that should be simple, e.g. Collections APIs.. aren't. I stopped trying after this realization.

I preferred the C# from 15 years ago compared to whatever is going on over there at present. If you're already indoctrinated into the ecosystem, I'm sure it's fine. Otherwise, buckle up - things are going to get choppy.

1 comments

How are collections in C# worse than in Go? In C# you have LINQ, in Go you're writing for loops around array slices.
Maybe I was using it wrong? As I recall, "the usual" APIs present in most other OO languages were not available when I tried to help a friend with a project 3 montjs ago.
Which collection APIs were you missing? Between the standard interfaces and their default implementations[1] and the extension methods to IEnumerable[2] you can do quite a lot in my experience.

[1]: https://docs.microsoft.com/en-us/dotnet/api/system.collectio...

[2]: https://docs.microsoft.com/en-us/dotnet/api/system.collectio...

You might've forgotten to reference LINQ and Collections.Generic in your project? Because C# definitely has good collection APIs that influenced many languages including Java Streams.
C# has very comprehensive collection API. More so than those languages.

Most languages copy c#

Which APIs were those?