it's a bit more than 100kb of js, but for prototyping it is very nice.
I wish more UI libraries where in the same style. You can always optimize the bundle later.
ale 45 minutes ago [-]
What does "HTMX support" even supposed to mean? HTMX is a drop-in library. Literally any html file "supports" HTMX.
axadrn 39 minutes ago [-]
You're right – HTMX works everywhere by default.
By “HTMX support” I just mean: the JS logic in components (e.g. tooltips, modals) auto-reinitializes after HTMX swaps.
So you can use components inside HTMX-driven UIs without worrying about broken behavior.
ipsum2 3 hours ago [-]
I had no idea JSX for Go would be so popular. (9.3k stars on the templ project). What are people using it for?
muspimerol 12 minutes ago [-]
Why do you say "JSX"? JSX is an HTML templating language for JavaScript. templ looks like an HTML templating language for Go. Every popular web backend language has an HTML templating language... so that it can produce HTML - is it really that surprising?
axadrn 3 hours ago [-]
Mostly for building typed web UIs in Go – instead of using html/template, which isn’t typed and feels oldschool. templ makes Go feel way more modern for frontend work.
anonzzzies 3 hours ago [-]
I know I am an old angry guy but I really don't want things to 'feel' (not sure what that even is) more modern; I have projects that bring me millions a year which are running for over 2 decades now and this kind of 'modern' is just obsolete next year. I like profit and not being bothered by updates every 5 seconds. I have a simple stack, my saas apps are violently fast and they run for decades without me touching anything but some bugs/features. The modern feel is not required and in fact detrimental to just making bucketloads of business value and company wealth imho. But then again, we never had investors, so I don't know how it feels to burn other people's money.
axadrn 3 hours ago [-]
Totally fair – stable, fast, boring tech is often the best kind of tech.
templ’s more for folks who want to stay in Go but need a smoother frontend experience for modern UI needs.
anonzzzies 3 hours ago [-]
Yep, that makes sense. I do prefer Go to TS really as I love typesystems but TS types often are completely unreadable. I am a Haskell guy and not entirely sure how they managed to make TS types this line noisy and, frankly, a struggle.
axadrn 47 minutes ago [-]
Is TS actually a thing? ^^
bananapub 2 hours ago [-]
These are weird things to complain about for templ - it’s very boring and stable and it just compiles to very boring Go code while 1) providing type safety for your templates and 2) being less annoying to compose things than template.html.
It definitely doesn’t feel like JSX or any other modern/exciting thing to me.
anonzzzies 1 hours ago [-]
The author and you are good at convincing me to use it. thanks and thats not sarcasm.
axadrn 48 minutes ago [-]
Appreciate that! Always happy to find common ground.
axadrn 1 hours ago [-]
THIS actually!
preisschild 1 hours ago [-]
I used the icons from templui, but haven't updated since a few weeks when the packages went internal, because you have to install its own cli now for dependency management.
Not a fan of that.
axadrn 50 minutes ago [-]
The CLI is just a small Go binary – you can install it once via `go install` and then run `templui add icon`.
It helps keep things consistent as the library evolves.
But yeah, I get that some folks prefer manual imports – all good!
avithedev 4 hours ago [-]
This is beautiful, thank you!
axadrn 4 hours ago [-]
You are welcome! Happy coding! =)
Rendered at 09:22:39 GMT+0000 (Coordinated Universal Time) with Vercel.
You really just paste these 2 lines in your html and that's it:
it's a bit more than 100kb of js, but for prototyping it is very nice.I wish more UI libraries where in the same style. You can always optimize the bundle later.
By “HTMX support” I just mean: the JS logic in components (e.g. tooltips, modals) auto-reinitializes after HTMX swaps.
So you can use components inside HTMX-driven UIs without worrying about broken behavior.
templ’s more for folks who want to stay in Go but need a smoother frontend experience for modern UI needs.
It definitely doesn’t feel like JSX or any other modern/exciting thing to me.
Not a fan of that.
It helps keep things consistent as the library evolves.
But yeah, I get that some folks prefer manual imports – all good!