gomponents VS vugu

I'm really happy you like it. :) And thank you for your comment, I really appreciate newcomer viewpoints especially.

Have a look at the `Classes` helper component already available: https://github.com/maragudk/gomponents/blob/main/components/...

Yeah, I'm not a total fan of the runtime panics, but it was a tradeoff where I chose in favour of API simplicity and readability. In practice, it works out well, because you catch any typos at development time.

I've had elements and attributes in separate packages before, but then you can't dot-import both packages and not have name clashes, and have to either prefix elements or attributes with the package name, which makes the code much less readable. Again, a tradeoff. :)

Gomponents:

I now always use https://github.com/maragudk/gomponents for frontend components (I'm the author of that library) together with HTMX (https://github.com/maragudk/gomponents-htmx), and it's just so much more fun and fast to work with.

However, there is an alternative to achieve React-ish components in Go using this package: https://github.com/maragudk/gomponents

reminds me of https://github.com/maragudk/gomponents

I’ve also started just rendering views from the Go backend. It’s so nice and simple when you don’t need an SPA (like in your case). I didn’t like the syntax of html/template though, so I started a small view component library. Maybe it would be useful to you too, wrote about it here: https://www.maragu.dk/blog/gomponents-declarative-view-components-in-go/

Are you speaking of something like: gomponents? I can see what it has to offer. I tried it for half an hour but did not feel that well about it.

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?