3 ms·
We reach out to Newtonsoft, because .NET also has a Python 2/3 problem and not everyone can be on .NET vLatest, or has the budget to rewrite code to use other p
by pjmlp 2y ago
We reach out to Newtonsoft, because .NET also has a Python 2/3 problem and not everyone can be on .NET vLatest, or has the budget to rewrite code to use other parsers.
- metaltyphoon 2y agoSTJ supports netstandard2.0
- pjmlp 2y agoIt does, but it also lacks feature parity, and someone has to budget the rewrite. https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/migrate-from-newtonsoft?pivots=dotnet-9-0 https://learn.microsoft.com/en-us/dotnet/standard/serializat...
- neonsunset 2y agoI wonder if Pjmlp would become happier if he was to stop working with companies using ancient stacks for no reason whatsoever. Luckily, companies like that are becoming a minority. You do not have to concern yourself with .NET Framework if you do not want to under free market economy :) Also, there was no Python 2/3 - it’s not comparable and there were no breaking changes in the language. You can’t be serious if you think these are equivalent.
- CRConrad 2y ago> companies using ancient stacks for no reason whatsoever. Luckily, companies like that are becoming a minority. Wow. I'd like to live in your world. Where I am, they seem to be the norm.
- pjmlp 2y agoNot everyone has the freedom to chose their employers, or consulting costumers. All companies whose main business isn't selling software have reasons to use ancient stacks, that isn't the money maker, what is deployed in production works, and there isn't budget around for a full rewrite. Also Microsoft could set the example, some of those products are theirs. Yes I am serious, library code also counts. If your identity wasn't so tied with .NET, maybe you would see the transition mess in a bit more impartial way, it is no accident that now they introduced AI based migration tool at Ignite, and are seeking companies willing to try it out.
- buzzardbait 2y agoFor legacy code that's already using a lot of Newtonsoft, I understand. For new code, developers should default to the first-party option. System.Text.Json is supported by .NET versions as old as Framework 4.6.1.
- pjmlp 2y agoLarge majority of consulting work is brownfield development, and new code must talk with old code as well.