You are viewing a single thread.
View all comments
1 point
*

System.Text.Json routinely fails to be ergonomic, it’s quite inconvenient overall actually.

JSON is greedy, but System.Text.Json isn’t, and falls over constantly for common use cases. I’ve been trying it out on new projects every new releases since .net core 2 and every time it burns me.

GitHub threads for requests for sane defaults, more greedy behavior, and better DevX/ergonomics are largely met with disdain by maintainers. Indicating that the state of System.Text.Json is unlikely to change…

I really REALLY want to use the native tooling, that’s what makes .Net so productive to work in. But JSON handling & manipulation is an absolute nightmare still.

Would not recommend.

permalink
report
reply

.NET

!dotnet@programming.dev

Create post

Getting started

Useful resources

IDEs and code editors

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

Community stats

  • 1

    Monthly active users

  • 100

    Posts

  • 25

    Comments