kyoto VS aleph.js

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

Check aleph if you want to use react with deno. But I'd suggest sticking with Node.js and Vite as you'll get less surprises.

Here's another thing: if you want to grow from this exact setup, use deno. It has support for import maps and don't require a bundler or a separate compilation step for typescript

https://deno.land/[email protected]/basics/import_maps

Maybe add aleph too (which is similar to nextjs)

https://alephjs.org/

Deno won't require nearly as much tooling as nodejs, but it still has tooling for the cases you need it.

There’s also https://alephjs.org, never used but pops up when you search for "deno react" so I assume is similar to nextjs.

Aleph.js is a full-stack framework in Deno, used as an alternative to Next.js. Aleph.js offers features like ES module imports, file-system routing, SSR & SSG, and HMR with a fast refresh.