4 ms·
Your information is very out of date. Microsoft long ago worked with the Newtonsoft.Json creator when introducing their native .NET replacement for Newtonsoft.J
by nathanaldensr 2y ago
Your information is very out of date. Microsoft long ago worked with the Newtonsoft.Json creator when introducing their native .NET replacement for Newtonsoft.Json. Performance in the new set of libraries is excellent as they rely heavily on the newer performance primitives like Utf8String, Span, etc.
- rqtwteye 2y agoI may indeed be outdated. Does Microsoft now support deserializing into dynamic for example?
- neonsunset 2y agoYou should never do that. Please do not, and I can't stress this enough, use `dynamic`. If you need DOM-style JSON handling, please use JsonDocument and JsonNode instead: https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/use-dom https://learn.microsoft.com/en-us/dotnet/standard/serializat...
- rqtwteye 2y agoThere are plenty of cases where dynamic saves a ton of code.
- neonsunset 2y agoNo, it never does. There are better containers than dynamic, that do not have its performance drawbacks and have way better UX. The fact that this does not raise an eyebrow is a legitimate concern over the state of the codebase that uses it!