Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introducing _sonic_, a maintained Jace.NET fork/successor #82

Open
vlow opened this issue Sep 21, 2023 · 1 comment
Open

Introducing _sonic_, a maintained Jace.NET fork/successor #82

vlow opened this issue Sep 21, 2023 · 1 comment

Comments

@vlow
Copy link

vlow commented Sep 21, 2023

Dear community,

Jace.NET seems to have reached a dormant state. Since we were using this code in production, we created our own fork in order to fix some bugs we encountered over the years. This year, we decided to move those bugfixes and performance improvements to a publicly accessible GitHub repository, in order to give the community a new actively maintained home.

We started with a new, clean fork, in order to being able to merge most of the open pull requests without major conflicts. We then added what accumulated over the years in our own repository. We also invested a lot of work to improve the maintainability, usability and performance over what we already had at our hands.

Since we made some notable API changes, sonic is now more of a successor to Jace.NET than a maintained fork. While this doesn't make it a drop-in replacement, it should be fairly easy to migrate to sonic.

If you find a bug in Jace, or would like to make use of a still unmerged pull request, you're welcome to give sonic a shot. It's available as NuGet package.

Also, if you have proposition for change, the sonic GitHub repo is actively maintained.

Best Regards,

Florian

@palhal
Copy link

palhal commented Sep 21, 2023

Wow, this sounds very promising. I spent quite some time looking for alternatives to Jace due to its lack of maintenance, but I couldn't find any good libraries that met my requirements. I'm eager to migrate when I'm back from paternity leave in a couple of weeks. I'm also curious if I will see any notable performance improvements as we are doing thousands of calculations every second.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants