The standard templating in Go has been good enough for my small projects, and I usually avoid adding libraries if I can help it. But seeing this makes me want to try it just to see how it compares.
there's an obvious typo of a variable name in the template "Titl" instead of "Title". Program compiles. Parse() succeeds. It just fails at runtime (outputting "<title>" and stopping. My understanding is that a Templ equivalent would probably end up with a compile error much earlier on (and probably more obvious in your IDE as well).
There is another class of template bugs that comes from input data, that's what I'm referring to. The validation catches it before rendering
people have a resistance to increasing tooling, and especially learning a new syntax or language, for a small task in a larger project
Since we test already, adding a test is often a much easier ask and lift
on top of that, you still need to validate inputs and test rendering with Templ anyway
If this sounds to the reader like a defense of Go templates... it isn't.
Plus, I would agree that while it can do almost anything you want, that doesn't mean it always does it in a good way, or in a way that makes sense if you aren't a programmer. It's a pity. There's some power there, and I like the attempt at making templating safe, but it could really use a v2.