router design.

[gedw99]

htmxgo has a router that is generated by parsing the golang AST.

https://github.com/adhocteam/pushup is a htmx golang system that is similar in some ways and has some nice things om top of that, as well as some painful problems too ( like all comparisons ).

Does dynamic restful routing:

https://github.com/adhocteam/pushup/tree/main/example/app/pages/projects/%24pid/users

Does compilation on the fl.

https://github.com/adhocteam/pushup/blob/main/_runtime/README.md

There are some other interesting things in there like a DSL for HTMX, to reduce the boiler plate, which htmgo could one day evolve to, but that a big jump.

I used it for a few hobby projects.

Its definitely worth a look for htmgo ....

[maddalax]

What ideas are you thinking of specifically that htmgo could take from that project? Currently we already support dynamic paths and automatic route gen

I don't plan to do a DSL because then it ends up too much like templ, which then I'd just use templ

[gedw99]

yeah dsl is fragile.

the only thing about both was that real time compile times gets slower aver time .

I work on system to compile each page down to WASM, and run off WASM on server. This keeps compiles times constant. Used wazero to run it . And could also run on client .

[maddalax]

Yeah the live reload speed as the app gets bigger is definitely something I'm worried about, I've been researching some possible ways to solve it but none look amazing so far

Wasm is interesting but it wouldn't quite work for html that has server side data fetching logic in it or server side only computations

[maddalax]

Added an issue here to keep track of that: #52