-
Notifications
You must be signed in to change notification settings - Fork 9
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
JavaScript support #11
Comments
QuickJS support is currently planned; As for WASM3, I will look into it. |
What about the SerenityOS JS engine? it seems complete and its fast. |
Source and blogpost from developers here https://github.com/SerenityOS/serenity/tree/master/Ladybird Its got a HaikuOS port so I don't think it'll be so difficult, check the build docs here: https://github.com/SerenityOS/serenity/blob/master/Documentation/BuildInstructionsLadybird.md |
It isn't optimized as much as quickjs and Quickjs is just much more mature. LibJS is very promising, but not yet complete, while QuickJS supports full Es2020, which is quite hard to accomplish |
Please just read the aforementioned blogpost |
https://github.com/bellard/quickjs Not updated since 2022, 70 issues open |
@xplshn what blog post? |
@xplshn that is not a blog post, however LibJS just got JIT compilation! That is awesome for a js engine that's less than 60KLoC. Also at this point lets use libwasm for wasm, even tho I think wasm3 is still both smaller, faster and more complete, plus it is maintained and written in c99. |
@xplshn another update: QuickJS just got updated! The project is still alive! |
Nice javascript support would be awesome. At least in my opinion, https://bellard.org/quickjs/ is the best option. Pure, portable C and most importantly, it supports ES2020, meaning Async/await and many nice, modern features are easily available, in contrast to Duktape which supports only the very old ES5 and is very slow compared to quickjs.
Also, not to be too ambitious, but https://github.com/wasm3/wasm3 might be an idea for WASM in the future too ;)
The text was updated successfully, but these errors were encountered: