vugu VS hotwire-rails

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?

Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.

For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."

https://htmx.org/

https://hotwired.dev/

For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).

I was recently interested in similar topic. Here are 3 similar solutions I found:

* https://htmx.org/

* https://unpoly.com/

* https://hotwired.dev/

My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:

* https://htmx.org/essays/hateoas/

* https://htmx.org/essays/locality-of-behaviour/

At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.

I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).