←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 1 comments | 11 Nov 25 15:44 UTC | HN request time: 0s | source
Show context
kurokawad ◴[12 Nov 25 09:48 UTC] No.45898241[source]▶
To me, it's pretty much unbelievable that Microsoft introduces an agent framework while for JSON serializing third-party Newtonsoft is still the go-to.

Edit. I was not aware that the gap between System.Text.Json and Newtonsoft narrowed, take my comment with a grain of salt, please!

replies(5): >>45898252 #>>45898257 #>>45898281 #>>45899376 #>>45904557 #
monerofglory ◴[12 Nov 25 09:54 UTC] No.45898281[source]▶
The go-to nowadays is System.Text.Json, developed by the same person as Newtonsoft.Json, built in to .NET.

Newtonsoft.Json as the primary JSON serializer (at least in every place I've worked) has NOT been the case versus System.Text.Json for years. Though it certainly used to be the case.

replies(2): >>45898298 #>>45902502 #
kurokawad ◴[12 Nov 25 09:56 UTC] No.45898298[source]▶
Uh okay! I was not aware of this. Thanks for pointing that out. Why is there so much difference in the NuGet downloads between both libraries tho?
replies(4): >>45898424 #>>45898540 #>>45898548 #>>45905845 #
1. akoeplinger ◴[12 Nov 25 10:31 UTC] No.45898540[source]▶
System.Text.Json ships as part of the shared framework in recent versions of .NET so for most users it won't be restored from nuget.org