v8go VS deno

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.

Deno 2 has arrived, bringing many features and improvements that have developers reconsidering their reliance on Node.js. While Deno currently holds a smaller share of the market, with 1.9% of developers using it compared to 40.8% using Node.js according to StackOverflow's 2024 survey, its advancements in TypeScript support and ECMAScript modules (ESM) showcase its potential. The community is eager to see how Deno will continue to evolve and if it can gain the traction needed to stand alongside Node.js as a viable alternative. Explore Deno 2's capabilities and assess its readiness to take center stage.

but i digress, in this post i will try to go over the points of Jamon in his thread thats talking about Bun, and how that is achieved in Deno.

JSX can become valid, standardized ECMAScript syntax.

But first we need a valid syntactic sugar transformation, which I propose here.

Then we need to implement it in things like babel[0] bun[1] and deno[2].

Then, frameworks would adopt it as an optional alternative implementation.

Eventually, it could gain widespread support and become standardized.

[0] https://github.com/sdegutis/vanillajsx.com/blob/main/site/un...

[1] https://github.com/oven-sh/bun/issues/13630

[2] https://github.com/denoland/deno/issues/25312

Ha, in what I believe Ryan's first talk about Deno, he mentioned something about avoiding cute features or so, then he said Deno has URL-based imports "because they're cute". It didn't take long for someone to raise it up in 2018:

https://github.com/denoland/deno/issues/195

We've come full circle :)

So, does that work now? Can we simply npm run test? Really? Well, almost. Unfortunately, Node, in comparison to other runtimes like Bun or Deno still is JavaScript only, so we have to transpile from TypeScript it to JavaScript first.

Deno

NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.

https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.