graaljs

> All JavaScript regexes engines that we could find, except one, use a backtracking implementation strategy [Chromium 2009; DukTape 2013; Hermes 2022; MuJS 2014; QuickJS 2020; WebKit 2018]. The exception is V8... Well, maybe there's another: TRegex [1] in GraalJs [2]. [1] https://github.com/oracle/graal/tree/master/regex / https://epub.jku.at/urn:nbn:at:at-ubl:1-24940 [2] https://github.com/oracle/graaljs

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

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

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

That's right, we will be able to cut it down in the future. Let me explain why: 1. Enso compiler bases on GraalVM which is 400Mb (packed)[1]. 2. The package contains GraalVM implementations of Python[2], R[3], and JavaScript[4] compilers, which weight 150Mb, 70Mb, and 50Mb respectivelly. 3. The package contains OpenCV library, as Enso has built-in bindings for it, which is 200Mb. 4. The rest (approx 200Mb) are core Enso libraries and tooling. We will be able to cut it down in the future as soon as we release Enso Marketplace which would allow you to install these things on-demand. [1] https://github.com/graalvm/graalvm-ce-builds/releases/tag/vm... [2] https://github.com/oracle/graalpython [3] https://github.com/oracle/fastr/releases/tag/vm-21.1.0 [4] https://github.com/oracle/graaljs

GraalVM's JS engine[1] is an implementation of ECMAScript 2021 and as such, it's a drop-in replacements for Node.js and npm. It also supports some Nashorn features for interop with Java, but for many things to work, you need to enable it explicitly, especially the compatibility mode flag (`-Dpolyglot.js.nashorn-compat=true`). See https://github.com/oracle/graaljs/blob/master/docs/user/Nash... [1] https://github.com/oracle/graaljs

The GraalJS license is apparently similar to MIT: https://github.com/graalvm/graaljs/blob/master/LICENSE "The Universal Permissive License (UPL), Version 1.0" And about the UPL: https://tldrlegal.com/license/universal-permissive-license-1... "... including an explicit patent grant, clear ability to relicense ..."

Hasn't Nashorn been superseded by GraalJS? Is this just for those who are stuck with Nashorn, or will there be new development? GraalJS is ECMASCript 2020 compatible and is said to rival V8 on performance, so I would've thought it the obvious choice for new projects going forward. https://github.com/graalvm/graaljs Edit: found more info about this release in the initial announcement: https://mail.openjdk.java.net/pipermail/nashorn-dev/2020-Oct...

> Can someone please give a sober explanation of what GraalVM, is and how Truffle works? GraalVM is basically a JVM with a new compiler, the Graal compiler. Truffle is the language implementation framework for GraalVM and designed to build AST interpreter. The Graal compiler can optimize Truffle ASTs through partial evaluation (see "One VM to rule them all" paper [1]), and produces machine code directly without using Java bytecode as IR. > how do JS semantics get expressed in a Java VM? Graal.js comes with a parser for JavaScript code that generates a Truffle ASTs for a given JavaScript program. JS semantics are defined within the AST nodes (see [2]). > What does a getProperty instruction look like? I think getProperty is implemented in `CachedGetPropertyNode` [3], but I am not sure as there are multiple other property-related nodes. > Ho

Bear in mind Deno isn't the only competitor. GraalJS can run all NPM modules on top of the JVM, in fact it supports both "pure" running JS on top of the JVM and also provides a mode in which it replaces V8 in the original Node binary, for extra compatibility with e.g. native extensions. This gives you at least three major tech wins: 1. Interop with the entire Java ecosystem and also as other Graal languages improve, with them too (e.g. Graal's Ruby support is pretty great, Python is maturing) 2. Extremely efficient and scalable pauseless garbage collectors. 3. Ability to do shared-memory multi-threading by sharing Java objects between workers. And soon via Project Loom there'll be very light weight fibers too i.e. you can write your code in a fully blocking style, no promises or async/await, but it'll be just as efficient as Node. It can

This benchmark mainly measures the performance of the HTTP parsing and database libraries, often in a suboptimal default configuration. In node land, they're admittedly not amazing, but nothing about the language prevents them from being better. For example, for a long time, the only reason that node was slow on these benchmarks was the built-in URL parser. Replacing it with this carefully written module https://www.npmjs.com/package/fast-url-parser resulted in 2x improvements on the benchmark. I haven't looked closely at the situation nowadays but I imagine its still quite similar with lots of low hanging fruit lying around and stalled due to backward-compatibility concerns. For proof find "es4x" in the benchmark list, which basically replaces the entire stack of HTTP parsing and database libraries with the ones from vert.x and runs JS o