Go plus HTMX is becoming a real alternative stack
The 'How I use HTMX with Go' thread drew enthusiastic comments from developers who have moved away from React-heavy stacks. The 'GUS stack' (Go, HTMX, SQLite) was named and described as a complete toolkit for building real apps without the complexity overhead of modern JavaScript frameworks. Multiple commenters mentioned pairing HTMX with Go's html/template package or the a-h/templ library for type safety.
This is not new, HTMX has been a HN darling for a couple of years. But the enthusiasm in this thread felt less like novelty-seeking and more like people reporting back from production. The specific praise was for being able to build 'actual pages' again, which points at a genuine frustration with the SPA mental model for apps that do not actually need it.
The counterpoint is real: HTMX works well for certain patterns and badly for others. Highly interactive, stateful UIs still push you toward something like React. But the number of apps that actually need that is smaller than the ecosystem would have you believe.
So what?
If you are a small team building an internal tool, a simple SaaS, or anything where the UI is mostly forms and tables, the Go plus HTMX stack is worth a serious look. You will ship faster, hire more easily from the Go talent pool, and avoid a category of JavaScript complexity that has real ongoing maintenance costs.