pushup VS templatecheck

I think this is adding unnecessary complexity. One of the reasons developers gravitate towards a framework like Alpine or HTMX is to write less JS and go back to enjoying HTML. Of course there are a lot of use cases that require custom JS scripting. But bootstrapping a project with another Go web framework and adding Alpine is also trivial. But keep going and follow your vision. I love these types of projects. Check this one out:

https://pushup.adhoc.dev

It's got some unique ideas.

This strikes me as incredibly clever.

The compiler and code-generation implementation seems equally straightforward and complex, my mind is racing trying to build a mental model of the whole thing.

The code generation comes after a feature-packed parser and "compilation" step. Emitting go source code is nice because subsequent compilation tells you if its valid or not. I'm wondering if there is a specific reason the "framework" source code is emitted via a series of printf calls[0]. A library of go template "fragments" might be easier to manage (and debug).

[0] https://github.com/adhocteam/pushup/blob/0519a782c1c9fc79877...

Looks interesting! There's a certain point where templating languages aren't flexible enough, and with Go many projects end up with a ton of custom template functions. I've been working on a web app for a few months now and at the start of it would have liked this, but now use "normal" Go templates and https://github.com/jba/templatecheck to bring runtime safety to templates, but that project has limits too.