graaljs VS cowasm

I would guess that depends on the licensing context in which it will be running, since Rhino is MPLv2 <https://github.com/mozilla/rhino/blob/Rhino1_7_14_Release/LI...> and OP's repo is MIT whereas Graal is UPLv1 <https://github.com/oracle/graaljs/blob/graal-23.1.2/LICENSE>. GitHub's license gizmo claims it is OSI/FSF approved, but Oracle gonna Oracle and they for sure have more lawyers than you do

graaljs

Here: https://github.com/oracle/graaljs

It's by Oracle: https://github.com/oracle/graaljs; seems to be built to interop w/ GraalVM based languages/services

If you need you can run JavaScript from within Java using Graal.js or Nashorn. To evaluate dynamic user input (Strings) you could also use a ScriptEngine (e.g. JavaScript) or dynamically compile inputs to Java using the JShell API.

That's just incredibly cool, my congratulations!

Foremost, my apologies if this is a nonsensical question. I haven't been soaking in the WASM ecosystem enough to know how much WASM is "just" JS versus ... something else.

Caveat aside, I saw one of the commits mention jython, which notoriously has ancient (and probably incredibly incomplete) python 2.x support; do you know if python-wasm would run on top of GraalJS (https://github.com/oracle/graaljs#nodejs-support)?

Separately, do you want issues related to zython.org in the cowasm issue tracker? It returns 405 (method not allowed) over and over on POST https://zython.org/python-wasm-sw/read-signal for me

Must be a fork because I found my own commits haha

https://github.com/oracle/graaljs/commits?author=styfle

Discussion reference https://github.com/oracle/graaljs/issues/239

For fun, I ported much of BSDutils to WebAssembly. Code [1] and live demo [2]. It was much, much easier porting BSDutils than GNU coreutils, since the source code is often much smaller, and hence easier to read and understand with simpler dependencies.

[1] https://github.com/sagemathinc/cowasm/tree/main/core/coreuti...

For what it is worth, I also care about building this with zig. https://github.com/sagemathinc/cowasm/blob/main/packages/sql...

If it fits your needs and is working, then fine. Please remain aware of a different approach to what pyodide is doing based on perceived weaknesses in pyodide.

CoWasm supports WASI right now via this library https://www.npmjs.com/package/wasi-js, which I actually develop as part of CoWasm . One unusually thing I did, which goes beyond what emscripten does, is I implemented a quite a bit of posix functionality, often by writing extension code to nodejs and calling it from Javascript, because there's a lot of POSIX that Node.js doesn't expose. This only works on Mac and Linux and is also available standalone in this library https://www.npmjs.com/package/posix-node, which is implemented in Zig. You can get a sense of the scope of POSIX functionality that goes beyond what WASI defines here: https://github.com/sagemathinc/cowasm/tree/main/packages/ker...

One motivation for doing this is to try to get the full Python test suite to pass, including all the functionality that involves subprocesses, posix calls, etc. I've only got to about 85% at this point. It can be a ton of tedious work, but at least Zig helps impose some discipline (e.g, it doesn't let you ignore handling errors until later), and makes it easy to test compilation for all supported targets on every change (due to excellent cross compilation support).