I wouldn't bet on it, https://devblogs.microsoft.com/dotnet/try-the-new-system-tex...
Also try to talk about Java 17 to clueless group of devs still delivering stuff into production with Java 8 in 2021.
Id say it’s part cluelessness and it’s part that they just don’t care. They’re comfortable with 8 and don’t want to learn anything new (even if 8 is a slower runtime).
I fear that the community will never move on past 8.
This would be the 2nd of 2 that I was referring to. The first would be Newtonsoft.Json.
You have to modify code using System.Text.Json for the code generator based way, and it doesn't support all the features, enjoy the comments section.
> and it doesn't support all the features
I think there was a misunderstanding.
We do not use System.Text.Json because it doesnt support everything Newtonsoft.Json does. At no point did I intend to make the claim that these were somehow compatible implementations.
Our shop is stuck on Newtonsoft until Microsoft realizes that polymorphic deserialization is actually a really useful thing and not just a pedantic security concern.
This is why I like the slightly more walled-in gardens of the JVM and CLR. For instance, when someone is talking about JSON serialization in C#, you could bet your life that they are referring to one of ~2 specific libraries and sets of methods.
It is a lot easier to build a community of shared understanding when everyone is playing the same game every day.