todomvc VS hlive

I'm working on https://github.com/atdiar/particleui An example of how the code looks would be: https://github.com/atdiar/todomvc

TODOMVC example in Go w/ particleui

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