-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add a note that the js backend is both experimental and unmaintained #103
Comments
I just tried to follow the instructions from the site on setting up rakudo.js, and the npm install fails entirely (might be on a prereq) I would recommend we remove the link to rakudo.js until it works, and also have https://www.npmjs.com/package/rakudo updated to refer to Raku, not Perl 6. - I was unable to find the source of that npm package. |
I can do the rakudo.org changes. |
Changes to rakudo.org are done. |
@dontlaugh, @andinus It seems that rakudo.org isn't updated. Is there any step I need to perform in addition to pushing to master? |
Hi @patrickbkr , yes changes are pulled manually, currently justin does them as part of pushing a release. I should automate this, I'll try to do that sometime soon. I've updated the website now. |
Change was 68d471b |
Thanks @andinus! |
Currently, the website lists the javascript part of raku/rakudo as an normal part of the whole language, which leads to outside viewers assuming that it is maintained like the rest of raku/rakudo, while this is clearly not the case in the moment.
It therefore should be added a notice that usage of the javascript backend / rakudo.js is experimental. It might even be of benefit to move the javascript tab from the top of the downloads page to the bottom under a new section "Experimental".
Maybe it also should be discussed if it is to be marked as "unmaintained" as it seems that way as no-one seems to work on it currently, which might be of benefit for an outside viewer to decide if they want to evaluate using rakudo with javascript or not.
The text was updated successfully, but these errors were encountered: