graaljs

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

No, not really a fork. GraalJS is a new independent from-scratch implementation of JavaScript. It uses a pair of radically different execution and optimisation techniques known as self-specialising-ASTs, and partial evaluation, and runs on the JVM. But a sibling project, Graal-Node.js, does include vendored code from Node.js in order to be compatible with Node.js applications. That's where the commits come from I'd guess. Compare: https://github.com/oracle/graaljs/tree/master/graal-js https://github.com/oracle/graaljs/tree/master/graal-nodejs

Must be a fork because I found my own commits haha https://github.com/oracle/graaljs/commits?author=styfle

Is GraalJS a fork of Node.js? Because I doubt Ry would write this article if he was one of the top contributors to GraalJS which is what this graph says: https://github.com/oracle/graaljs/graphs/contributors