Utf8Json fork discussions

[gordrs]

This is a discussion that is a follow on from neuecc#223 to discuss the fork.

[DamianSuess]

Thank you for kickstarting this again! Can't wait for the NuGet

[vilinski]

I think 1.4.0 is totally ok. But would be also cool to take some more critical PRs. Still waiting for #220.

[gordrs]

@vilinski Thanks for flagging this one to me, I'll test this one out this evening and merge it in before the nuget package is released.

[gordrs]

I merged that in and included it with the 1.4.0 release. https://github.com/Cryptisk/Utf8Json/releases/tag/v1.4.0

[vilinski]

You rock! But one drawback of other nuget name - packages, depending on Utf8Json have no benefits. For F# community it is Giraffe and Utf8Json.FSharpExtensions.

[gordrs]

True, that is a big drawback. Hopefully neuecc notices and we can get all this stuff merged in, I'd be willing to contribute as a maintainer upstream. Failing that, it would be up to those projects to point to this more updated package if upstream isn't going to get updated in the near future.

[phobos2077]

I really doubt nuecc will ever get back to work on this project. He has a track record of making an industry-leading tool, supporting it for some time and then suddenly abandoning altogether. This also happened with UniRx. I really hope some good people will make a similar fork of UniRx at some point, it's super useful and popular.

[vilinski]

well I'm afraid too, 2 years of inactivity, not a single reply on github or twitter is enought reasons to take a fork with the nuget name alltogether.
Can we just publish a Utf8Json NuGet again?