HaxeFoundation
How deprecated is Neko now?
Hi, I actually use Neko in a few projects and have some patches to the core and standard library.
Why was it deprecated? Is this simply an instance of a new maintainer needing to be found? Or should I make a hard fork of Neko and add my features to that?
Neko is deprecated because it was mostly superseded by Hashlink, so there is not much point in maintaining Neko anymore.
There was meant to be one more release (2.4.0) mostly for packaging reasons, but the current master branch includes a few bug fixes as well. Is it new features you're looking to add? Or bug fixes?
Primarily additions to the standard library, plus some typo and documentation fixes, and I think I modified some #defines and fixed some compiler warnings as well. There is one major change to the internals of the VM that I want to make, but haven't done yet. I have a todo/wishlist of features that I've picked at over time.
I never used Neko as a Haxe target, so I didn't know about HashLink. I have a Lisp compiler/interpreter I use for my projects that targets Neko that I've been working on finally packaging up for public release.
Primarily additions to the standard library, plus some typo and documentation fixes, and I think I modified some #defines and fixed some compiler warnings as well. There is one major change to the internals of the VM that I want to make, but haven't done yet. I have a todo/wishlist of features that I've picked at over time.
Beyond the typo/documentation fixes, it is probably unlikely for new features or a large internal changes to be merged in.
Hashlink was made with the problems and limitations of Neko in mind, so it might be worth having a look at the details of Hashlink before changing the internals of Neko:
https://haxe.org/blog/hashlink-indepth/ https://haxe.org/blog/hashlink-in-depth-p2/
Although, I'm not sure how suitable Hashlink would be for a custom language.