> but I already have all this code relying on Newtonsoft-y things :( Welcome to the dungeon... Our jailer is polymorphic deserialization. We've got many gigaby

> but I already have all this code relying on Newtonsoft-y things :( Welcome to the dungeon... Our jailer is polymorphic deserialization. We've got many gigabytes of Newtonsoft JSON in prod with that $type property throughout. Any place I can use System.Text.Json I will, but there are a few legacy usages that absolutely won't work. At this point, I'd like to rescind any expectation/desire for Microsoft to support polymorphic deserialization in their JSON library... It was a super powerful trick to get us to the next step, but it eventually turned into a nightmare for codebase maintenance. Until we have this monster refactored, we won't be able to move most of our types into different namespaces or assemblies.