hlive VS live

I do a lot of wired stuff with server-side virtual DOM, and I've found Go a good fit. I don't think inheritance is a problem with designing a component library. I've used struct and interface embedding to share common functionality. (see Tag and Tagger, then Component and Componenter as sort of examples).

Poking through the repo at https://github.com/SamHennessy/hlive now. It's particularly interesting to me because I wanted to write a virtual DOM for something that did serverside rendering and clientside via WASM. I wanted to be able to parse a template language much like jsx or Angular templates for a delcarative syntax. A friend of mine I worked with years ago and I set up a 3 day hackathon. We went through some design work, decided we didn't have time in our lives to take on a project like this, and settled on using Go's html templating. I tried to reuse a lot of the concepts using a two pass method (since you can't hook into the parsing but can always register DOM listeners) thinking I could accept a little inefficiency in exchange for a lot less work. Finally, the weekend was over. We had some interesting ideas collected with some innovative new thoughts on state management, but he dove into his next project using Vue instead, and I haven't had time to continue.

I'd appreciate it if you tried to build something using this: https://github.com/SamHennessy/hlive

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.

You can see all those “live-” attributes in a small example above. We just say: “ live-click=’tempUp’ “ and Live implementation makes all bindings to our backend code and makes a websocket call for the appropriate Go handler.

LiveView implementation for Go raised the same type of feelings in me when I went through this for the first time.

And here it is, where LiveView programming concepts help us in a great way. LiveView uses websockets to create a persistent connection between the client and the server, which enables the server to push updates to the client in real-time. This allows developers to build interactive user interfaces that can update dynamically in response to user actions or changes in the application state, without the need for traditional page reloads or AJAX requests. LiveView programming style is based on this excellent Live project that is an implementation of the LiveView approach in Go.

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

I built it because I love building highly interactive web pages, but the current state of JavaScript leaves me cold. I got really excited when I saw what Phoenix was doing with LiveView and thought I could see the light at the end of the tunnel. There are already a couple of projects also inspired by LiveView (GoLive, live), but I had my own vision that I wanted to realise.