ssceng VS kyoto

We are working on providing better start experience. I understand that current quick start section is not working well and I'm working on it. Unfortunately, features overview requires more complex setup, rather than simple quick start section. You can find async example here: https://ssceng.codes/docs/quickstart.html#simple Lifecycle briefly described here: https://ssceng.codes/docs/concepts.html#lifecycle Anyway, we are only finished library landing page + documentation setup, as a basis for future improvements. Current documentation was copy-pasted from old README and need a huge rework. In a day or two, I'll upload small demo project with some examples of usage. For now, library landing setup is the only example of usage (https://github.com/yuriizinets/ssceng/tree/master/web)

the only thing i need to do is port the htmx code to golang and then cross compile to wasm for web and then to mobile and desktop. I am currently seeing that there are other htmx style systems out there that are already written n golang. for example: https://github.com/kyoto-framework/kyoto

But this baby here https://github.com/kyoto-framework/kyoto is in the early development stages, which is a nice approach imho.

htmx requires you to return markup for specific components. So, you’ll need to maintain component template definition in two ways: embed directly into page template, and serve it as an api. IMO htmx is cool, but requires some tooling around it to simplify work. Our team is developing and using kyoto library, focused on server rendering and components approach: https://github.com/kyoto-framework/kyoto