hlive VS golive

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

1) change html content on the fly based on user input without redirects. I guess I found something relevant here to help me out, but I haven't tested any of it yet and keeping my options open for now. I know javascript frameworks are the usual go-to for that stuff, but I'd like to play around with Go before diving into another language.

I stumbled on two options: - GoLive (similar to Phoenix LiveViews) - Vugu (similar to Vue)

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.

As for LiveView ports or code inspired by LiveView in Go there is also https://github.com/brendonmatos/golive but I haven't had the chance to use either yet. If either are more or less a direct port (as much as they can be given language constraints) then I'd bet on them over hotwire. The Elixir community has already worked through most of the hard problems hotwire will encounter down the road with more use.

I'd like to suggest GoLive (https://github.com/brendonmatos/golive). It's a new project with an owner that is very open to pull requests. I've been sending PRs and it's a fun project to work on. What is GoLive:

GoLive Repo https://github.com/brendonmatos/golive