Exactly! Which is why using AI to do spikes and then writing the code anyway is a fitting revenge. :)

BTW. This, actually, is the first comment I got; this blog is brand new. Thank you.

You're welcome!

I'm hoping to get some early feedback for the API: https://github.com/bilus/live-templ/releases/latest/download...

I've braced myself for ANY feedback you can send my way, so go ahead. :) I don't work to work on this in isolation.

I'm personally quite comfortable with the API so far, the only real doubts is error handling, i.e. IncTemperature from the PDF can optionally return an error and if that happens, it kills the session (state for an open browser tab) and restarts it with no state. Because errors need to be handled as regular state in LiveView. But it may be counterintuitive for Go developers. If anyone is interested, I can go into more details on this one.

Couldn't agree more!

Thanks, good read. :)

It this case, this is more like a foster parent; Oya started as a part-time open source project, then Tooploox sponsored further development after having used it internally.

It was created as an independent open source project, then used internally @ Tooploox, then development got sponsored by Tooploox so it does make sense from our (very subjective) pov.

But I agree AFTER it got moved to Tooploox Github it looks kinda self-serving.

Thanks for the history lesson, but that history is missing from your website. Others may have the same thinking as I have without the history lesson.

I would take it out. It seems a bit silly :)

I think this is the key question we should address right there on the home page. Thank you for this.

It's language-agnostic. But point taken, thank you!

Thanks, I appreciate the honest feedback! We'll try better.

No. But it's a very valuable question; it shows we clearly have a problem with making it clear.