bud VS goja

Yeah. It seems like Bud is the best option I have to get what I want: https://github.com/livebud/bud/

Hit me up if you have a longer time horizon and want to give https://github.com/livebud/bud a shot!

Awesome!

This would be such a game-changer for server-side rendering Javascript in Go with V8.

I'd love to integrate this into Bud[1].

[1] https://github.com/livebud/bud

I've also been seeing updates on this project, which is kind of preferring Svelte https://github.com/livebud/bud

https://github.com/livebud/bud - similar idea, but uses Svelte (a JS framework) to do the front end stuff. It’s smart enough to render the JS stuff on the server when possible, so you end up with the best of both worlds.

https://github.com/livebud/bud this framework is achieving SSR in go. Not Vue specifically last I saw, but maybe you can draw inspiration from what they did https://www.reddit.com/r/golang/comments/uoxocj/bud_the_fullstack_web_framework_for_go_developers/i8ke92h/?utm_source=reddit&utm_medium=web2x&context=3

See https://github.com/livebud/bud to learn more.

Just to clarify: Fymo is taking the same approach as Bud. See: https://github.com/livebud/bud/discussions/248 for details 🙂

An open-source GoLang project also took the same approach, livebud/bud.

I know how to create APIs. I actually don't wanna do an API link with the front end. You can check a framework built in GoLang, livebud/bud in Github. Seeking something like that, 'cause the project is still being developed.

We recently switched from Node.js + Mathjax for rendering latex to Goja (https://github.com/dop251/goja) + Mathjax, and surprisingly it worked really well. We did this because the app is already 99% golang, and this allows us to eliminate the remaining non-go pieces like Node.js. And yes, we tried go-latex, but it's not nearly as feature complete as Mathjax.

I've been writing my own linter that's supposed to check projects regardless of the technology (e.g. something that focuses on architecture and conventions, alongside something like Oxlint/Oxfmt and Ruff and so on), with Go and goja: https://github.com/dop251/goja

Basically just a bunch of .js rules that are executed like:

  projectlint run --rules-at ./projectlint-rules ./src

I looked at goja [1] as that's a pure Go engine that's advertising only as ES5. ES6 modules seem to have been implemented only in the sobek fork [2] so there's some hurdles of using it in practice right now.

The detailed report [3] is quite nice tbh, I think that would be some nice document to refer to.

[1] https://github.com/dop251/goja

[2] https://github.com/grafana/sobek

[3] https://github.com/ivankra/javascript-zoo/blob/master/engine...

And yes I know that Grafana has a fork called Sobek that has ESM support, but it is tailored for k6 and they don't have plans for making it easier to use. [2]

[1] https://github.com/dop251/goja/issues/348

The benchmark sets up a custom HTTP endpoint /fibonacci?n= using the same slow recursive Fibonacci implementation for both, PocketBase and TrailBase. This is meant as a proxy for a computationally heavy workload to primarily benchmark the performance of the underlying JavaScript engines: goja for PocketBase and V8 for TrailBase. In other words, the impact of any overhead within PocketBase or TrailBase is diminished by the time it takes to compute fibonacci(N) for sufficiently large N.

We will be using the goja library, a JavaScript VM written in Go, to execute JavaScript code. This setup allows developers to provide custom transformation logic for http payloads and headers.

dop251/goja