vecty VS vugu

Vecty

It depends on how specifically you don't want to write HTML/CSS/JS and how broad your definition of "frontend" is. There are a handful of all-go frontend frameworks such as Vecty and Vugu of varying maturity and completeness. Then there's other libraries that more or less have you write HTML tags in go, such as go-app.

It draws on Go's syscall/js library as inspiration, which is pretty powerful (I wrote a pretty popular React-like framework using it a while back.)

A note on wasm: I'm building a hobby project with it right now and have tried different frameworks, I tried vecty which is nice to compile but full of bugs and unexpected behavior. I'm now on vugu which works better but is still harder to work with than a JS framework.

https://github.com/hexops/vecty/ is a framework for developing dynamic web frontends in Go. It's not production-ready, and will likely get some rewrites once generics drop, but it's pretty neat (I'm a contributor).

There's Vecty, though it's likely to get a bit of a redesign once generics drops.

How does it compare to https://github.com/hexops/vecty or https://github.com/bep/gr ?

Reminds me of Vecty from the GopherJS project: https://github.com/hexops/vecty .

I can't share any of my own examples, but most of the work I do was originally based on Vugu[0] which is open source. It is loosely modelled on Vue, so template files have both HTML and Go source (for the view / front end / ui handling) in the one file.[1] The code I have written has since diverged a bit from Vugu but at its core it's handled the same way.

People are still working on Vugu (you can check the issues / branches) but there hasn't been a new release in a while; it's still somewhat experimental.

[0] https://www.vugu.org/

. Web backend (with various frameworks available) . Web Assembly (one of them is vugu framework) . Microservices (some frameworks: Go Micro, Go Kit, Gizmo, Kite) . Fragments services (Term mentioned by @jeffotoni in a microservices discussion group) . Lambdas (FaaS example) . Client Server . Terminal applications (using the tview lib) . IoT (some frameworks) . Bots (some here) . Client Applications using Web technology . Desktop using Qt+QML, Native Win Lib (example Qt, Qt widgets, Qml) . Network Applications . Protocol applications . REST Applications . SOAP Applications . GraphQL Applications . RPC Applications . TCP Applications . gRPC Applications . WebSocket Applications . GopherJS (compiles Go to JavaScript)

Aside from Blazor there's already some other projects like Yew (rust), seed (rust), asm-dom (C++) and vugu (Go) and more that have decent followings and activity. A lot more (especially managed languages) are waiting for some features to come online like wasm GC and host bindings (direct wasm access to browser apis which includes the DOM). It'll take a bit of time, but it'll get there eventually.

Vugu

It depends on how specifically you don't want to write HTML/CSS/JS and how broad your definition of "frontend" is. There are a handful of all-go frontend frameworks such as Vecty and Vugu of varying maturity and completeness. Then there's other libraries that more or less have you write HTML tags in go, such as go-app.

Something like Vugu looks like it could have some potential.

There is https://www.vugu.org/ It's Vue, but Go instead of JS.

A note on wasm: I'm building a hobby project with it right now and have tried different frameworks, I tried vecty which is nice to compile but full of bugs and unexpected behavior. I'm now on vugu which works better but is still harder to work with than a JS framework.

If you have the option go for https://www.vugu.org/ and use the go language. Much better language started by google in 2006 vs JavaScript which was started in I think 1995?