It was a great experience, at least to the extent I needed it. What sold me on it is its support for template composition[1], something I've struggled with using the standard `html/template`. And I really like the idea of generating statically typed templates which are just Go functions in the end of the day. In theory, I can share them between many of my apps, especially as I'm using a monorepo for all my projects. This is yet to be tested though.

There are some rough edges around using `script` templates[2], for example it doesn't allow you to pass `this` and `arguments` from HTML event handlers[3]. This is not a show-stopper though, because you can always fall back to just defining your event handler in an HTML <script></script> block, albeit without type checking of the arguments and deduping the scripts. Also it hurts Locality of Behaviour which I'm a fan of.

That being said, I think it has some great potential. I can completely imagine people building fully-fledged UI libraries in this once component reusability is improved.

But the best part of using templ for me was that I could completely get rid of Node and NPM from my stack.

How was your experience?

[1]: https://templ.guide/syntax-and-usage/template-composition

[2]: https://templ.guide/syntax-and-usage/script-templates#script...

[3]: https://github.com/a-h/templ/issues/494