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.
9 Comments
starman@programming.dev · 4 pts · 3y
System.Text.Json
I'll miss FluentValidation but it's the only way to stop Newtonsoft.Json /s
Dumhuvud@programming.dev · 2 pts · 3y
STJ is a part of the standard library since forever though, who cares if it stays on NuGet
starman@programming.dev · 3 pts · 3y
Fair point
burt@programming.dev · 2 pts · 3y
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?
starman@programming.dev · 2 pts · 3y
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.
douglasg14b@programming.dev · 2 pts · 3y
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...
garam@lemmy.my.id · 1 pts · 3y
Text.json