quickjs VS engine262

This is a fantastic approach.

BTW, it looks like the js engine is "QuickJS" [0]. (I'm not familiar with it myself.)

I like it because sqlite by itself lacks a host language. (e.g., Oracle's plsql, Postgreses pgplsql, Sqlserver's t-sql, etc). That is: code that runs on compute that is local to your storage.

That's a nice flexible design -- you can choose whatever language you want. But quite typically you have to bring one, and there are various complications to that.

It's quite powerful, BTW, to have the app-level code that acts on the app data live with the data. You can present cohesive app-level abstraction to the client (some examples people will hopefully recognize: applyResetCode(theCode) or authenticateSessionToken(), or whatever), which can be refined/changed without affecting clients. (Of course you still have to full power and flexibility of SQL and relational data for the parts of your app that need it.)

[0] https://bellard.org/quickjs/

Considering the extremes of prolific developers gives interesting contrast to dogmas such as "functions/files should never be above x lines", where `quickjs.c` is 50k lines and has functions that are hundreds of lines long:

https://github.com/bellard/quickjs/blob/master/quickjs.c

(Obviously different approaches suites different circumstances.)

And some lightweight alternatives like Bellard's QuickJS (https://bellard.org/quickjs/) in C and Kiesel (https://kiesel.dev/) in Zig.

Built on a highly optimized JavaScript runtime powered by QuickJS, Query offers fast startup times and efficient execution. Its built-in caching mechanism further enhances performance by storing function responses, reducing database load and latency. This focus on speed makes Query a standout choice for server-side rendering, especially in applications with many components.

Where the previous SDK was built on top of the QuickJS JavaScript engine and the Javy runtime, the new SDK is built on top of the Firefox browser’s SpiderMonkey engine, and the Bytecode Alliance’s StarlingMonkey runtime and ComponentizeJS WIT bindings generator.

I'm currently using Bellard's QuickJS engine on a new TypeScript project.

engine262

Indeed. ECMA-262 has been implemented using JavaScript https://github.com/engine262/engine262.

Node.js is not the only JavaScript runtime. JavaScript runtimes have been written using JavaScript alone, see engine262. There is also Deno, QuickJS, txiki.js, Bun, none of which use COmmonJS by default, SpiderMonkey, et al.

for an interpreted language like JS, this project is really nice https://github.com/engine262/engine262. More or less 2 parts: parser and evaluator

That is a bit complex, so here's a list of JS engines: if you pick one written *in* JS, that would probably be most useful -- engine262 for example

then you might be impressed by https://github.com/engine262/engine262 as well

Engine 262

It's outside of what you asked for, but here's a JavaScript engine in JavaScript. Might make for some interesting bedtime reading!

Interesting to see a JS implementation written in JS:

https://github.com/engine262/engine262/

(The readme explains what the point of it is.)