quickjs-go VS v8go

quickjs-go/quickjs-go

Firstly, I used rogchap/v8go to execute JavaScript in a Go environment. I listed other options below.

Now the only issue I see is that someone who can't be bothered to install PHP and composer will probably not want to install node and npm either. If you could somehow run WASM inside an executable file (maybe something written in Go with https://github.com/rogchap/v8go ? Or an Electron App ?), all you'd need to do is download the executable file on any computer and double click it to start serving a Laravel project.

I only browsed for a wee bit, so take this with some salt, but it _looks_ like the framework is running a JS VM isolate alongside the Go server struct[1], which gets called with whatever script file is being rendered. Since it looks like the render files are, at least in the case of Svelte, individually compiled JS files that are SSR rendered via the V8 isolate, I _believe_ you're correct that there is no CSR (though there might still be JS-hydrated code if the Svelte component included something involving an interactive component).

I think the idea is to ingest a JS "template" and spit out the rendered HTML+JS, kind of like traditional SSR templates, but it could be possible to shoe-horn in an entire client-side router that gets initialized as a DOM object somewhere.

[1] https://github.com/rogchap/v8go

https://github.com/rogchap/v8go is a viable option these days as well.

Plenti is a simple open source Static Site Generator (SSG) with a Go backend and Svelte frontend. Jim picked Golang because it is simple, quick and has the ability to generate a binary that can be run on any machine; and Svelte, well, for one, “Svelte is so hot right now” and also because of the power it gives developers to write simple HTML and CSS to create websites. Merging these two technologies was not an easy task, but with V8Go binding the two together, it’s a marriage that works.