This repository was archived by the owner on Dec 4, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 4, 2023. It is now read-only.
Status: UNMAINTAINED #328
Description
Activity
yeah I think this is the right thing to do... I think you have rights? go ahead and do so.
No I don't have permission to archive or pin issues.
But I'm happy to prepare an issue and a PR for the README changes.
I have gone through all issues here, just too make sure no thread was left hanging.
With the last bit of this done I'll push an update to the README and pin this issue.
I believe the same should be done for therubyracer, which already has an issue that I just pinned, and a small note that I think should be a bit more prominent.
- pinned this issue
on Dec 4, 2023 - changed the title
[-]Archive this repository and point to libv8-node?[/-][+]Status: UNMAINTAINED[/+]on Dec 4, 2023
libv8 hasn't been touched in 3 years and it's not very likely it will be again.
It has since been replaced https://github.com/rubyjs/libv8-node. It has binary distributions for more architectures and most importantly more modern versions of V8 (afaik up 11.3.244.8 in the current release).
I propose to archive this repository, pin either this issue (or another one explaining) and also add info to the readme.
-cc @SamSaffron