live

I was as well, but in the last years they really jumped ahead; it might be personal, but for me I cannot imagine going back. Especially when I now use nextjs or so, I scratch my eyes out. It's such an timewasting and frankly annoying experience compared to liveview, livewire [0], go live [1] and of course CLOG [2]. Edit; Blazor server[3] is another one [0] https://laravel-livewire.com [1] https://github.com/jfyne/live [2] https://github.com/rabbibotton/clog [3] https://learn.microsoft.com/en-us/aspnet/core/blazor/hosting...

Looks like there are a couple of attempts but my google fu didn't really yield a winner. https://github.com/while1malloc0/hotwire-go-example https://github.com/jfyne/live if that's the case, there is definitely an opening on the market for such tech. As someone who's been writing web apps since DHTML days, Livewire/Turbo feels like we've finally reached the future, although with caveats.

There is a port for Go: https://github.com/jfyne/live . However, the API is not nearly as clean and nice, and it's probably not as efficient as Phoenix either. But overall it's really made a number of applications much easier to build and it has allowed me to avoid mountains of JS.

There is https://github.com/jfyne/live which is probably what you're looking for.

I hate SPAs. I would never do another SPA again if it were up to me. It just adds too much mental context switching and overhead. I can develop fully server-side apps that are lighter, run faster, and at least 20% less development effort (I actually compared that for the same task: https://medium.com/@mustwin/is-react-fast-enough-bca6bef89a6). So why would I ever do an SPA again if it were up to me? I would use https://github.com/jfyne/live which is inspired by Phoenix LiveViews. This is my professional opinion, having many years of experience in both kinds of web apps.

I've been working on a Go implementation if you fancy trying it out https://github.com/jfyne/live