Support for System.Text.Json about jot HOT 4 CLOSED

It would be fairly easy to do, but I'm not sure if there's a benefit to it. Any pros/cons you can think of @daniel-rck?

from jot.

Maybe this can give you feedback: https://devblogs.microsoft.com/dotnet/whats-next-for-system-text-json/#choosing-between-system-text-json-and-newtonsoft-json

Personally I guess System.Text.Json will evolve more and will be faster than Newtonsoft's.

from jot.

I was put off by the number of dll dependencies that are download with it. The total size is roughly the same, though, so it's not much of a factor. For now I don't see a good reason to switch, but if one pops up, I won't mind.

from jot.

I know this is closed but now that System.Text.Json is more mainstream and relevant, do you think there would be a chance you could implement it? Could be as simple as having a core Jot package and then two separate ones, one for Newtonsoft Json and one for System.Text.Json, since it's just as simple as implementing IStore

from jot.