pushup

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...

> why not just mimic JSX Definitely considered that. Might be worth revisiting. > The big missing piece to me here is composability You zeroed in on the right things ;^) I have a draft note to myself about pages-as-components. I have some ideas (basically, mimic ASP.net Razor components at the moment). Having a compiler with full control of the page makes this easier to figure out. > without having to backtrack, since that last period is ambiguous in this grammar. It doesn't backtrack, it just looksahead at the next token: https://github.com/adhocteam/pushup/blob/main/main.go#L3692

I was inspired in part by Razor, although I'm not a C#/ASP.net developer. I just liked the way it looked and worked from examples I saw. I actually started with @ [1] but changed to ^ for 2 reasons: having to escape for email addresses (although in retrospect maybe it's not such a problem), and the admittedly cheeky ^ being the "up" in "Pushup" :^) [1] https://github.com/adhocteam/pushup/commit/04aa00bb5401bc93b...