←back to thread

.NET 10

(devblogs.microsoft.com)
484 points runesoerensen | 2 comments | 11 Nov 25 15:44 UTC | HN request time: 0.461s | 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 #
1. gf000 ◴[12 Nov 25 16:55 UTC] No.45902502[source]▶
Doesn't Text.Json have a much narrower scope and plenty of features supported by Newtonsoft not available?
replies(1): >>45905380 #
2. orphea ◴[12 Nov 25 19:48 UTC] No.45905380[source]▶
No, not plenty: https://learn.microsoft.com/en-us/dotnet/standard/serializat...