System.Text.Json
I'll miss FluentValidation but it's the only way to stop Newtonsoft.Json /s
this post was submitted on 13 Jun 2023
11 points (100.0% liked)
C Sharp
1532 readers
2 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
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
founded 1 year ago
MODERATORS
STJ is a part of the standard library since forever though, who cares if it stays on NuGet
Fair point
I feel like I'm too senior to ask this, and should know better, but my main responsibility is a .net framework 4.8 application, so I may have missed a memo. Why does Newtonsoft.Json need to be stopped?
It's fine on pre .NET Core 3.0 versions, but I've seen it used many times on later .NET versions, when there was no need to. Maybe my comment sounds to serous, I think that Newtonsoft.Json is still useful on older platforms.
Well I'm evil, so System.Text.Json.
Maybe after the whole world dunks on it feature champions devs will change their asinine stances on keeping it terrible...
Text.json