gomponents

> to extract the maximum power from htmx an HTML library that's embedded directly in your programming language is much more powerful. I'm actually using gomponents, but the maintainer doesn't like the vibe of adding attributes to existing nodes. https://github.com/maragudk/gomponents/issues/276 (I don't really understand his argument, but in general I'm in favor of maintainers doing what they think is the right thing; and in any case I'm using his work without paying, so not gonna complain.) But even if I had an easy way to add the attribute, the fact that I need to think about that extra step is a bit of extra friction HTMX imposes, which datastar doesn't.

there's a few attempts, templ[0], gomponents[1]. Not for cli apps per se but for web dev. 0: https://github.com/a-h/templ 1: https://github.com/maragudk/gomponents

If you mean “action=/foo” for a “form” tag, there is an “Action” attribute: https://github.com/maragudk/gomponents/blob/main/html/attrib...

I'm still fairly new to Go, but I've been iterating on the idea of approaching HTML as basic string generation and ditching all of the other complexity. I have a single function that generates HTML tags from name, content and property arguments. Everything else just builds on it. [1] I'm really curious to do some benchmarking and see how this compares to template-based HTML generation. It seems theoretically possible to accumulate raw data first and then build the document from top to bottom (instead of piecing together a lot of intermediate strings), but I'm not sure the complexity would justify the performance gains. I also just learned about `gocomponents` [2] in another thread here, which seems to be a similar idea with a substantial headstart. I could probably just switch to it, but I kind of like the idea of following a pattern inst

I use gomponents with go, which is very similar. The productivity increase is immense. https://github.com/maragudk/gomponents

I'm really happy you like it. :) And thank you for your comment, I really appreciate newcomer viewpoints especially. Have a look at the `Classes` helper component already available: https://github.com/maragudk/gomponents/blob/main/components/... Yeah, I'm not a total fan of the runtime panics, but it was a tradeoff where I chose in favour of API simplicity and readability. In practice, it works out well, because you catch any typos at development time. I've had elements and attributes in separate packages before, but then you can't dot-import both packages and not have name clashes, and have to either prefix elements or attributes with the package name, which makes the code much less readable. Again, a tradeoff. :)

Thank you for the mention! :) Relevant libraries, for those who want to dive directly into it: - https://github.com/maragudk/gomponents - https://github.com/maragudk/gomponents-htmx