The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:
https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q
this post was submitted on 21 Jun 2023
35 points (94.9% liked)
.NET
1462 readers
3 users here now
Getting started
Useful resources
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
Wikipedia pages
- .NET (open source & cross platform)
- .NET Framework (proprietary & Windows-only)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Type system rigidity, I started using TypeScript a lot over the last few years with FE work. TS is so much more flexible and expressive. I really wish that I could express constraints in C# as fluently as I can in TS
Enums really need more flexibility, unions, discriminated unions, left hand implicit type, better value support....etc
System.Text.Json still sucks, it's not greedy, no global setting , non-sane default,no expando support....etc it's awful to use.
Unstructured data in general is an absolute pain to work with.
Composability of tests is still super painful and verbose. Dynamic test generation is awkward and unergonomic. After doing testing and other languages that let you simply compose tests imperatively, C# testing is definitely painful.
IMHO C# is an acceptable language with an absolutely fantastic framework.
I love C#, but these are my primary gripes