fir VS pushup

Fir is an open source project, so if you are interested in contributing you can head over to their GitHub repository. You can also open an issue there if you encounter any problems you can’t solve on your own.

This example has most of the scenarios you have called out: https://github.com/livefir/fir/tree/main/examples/fira. Fir aims to limit itself to rendering templates on the server and making it available for all subscribers as a browser CustomEvent which is consumed by alpine.js for more complex interactivity. The expectation is the that the developer handles it via either alpine.js plugins or standard JS code.

I have been using this so called template fragments to in a reactive library for building web apps: https://github.com/livefir/fir It mostly works but still a work in progress

Been working on a html over the wire library in Go: https://github.com/livefir/fir. It mostly works but still work in progress

Then use something like Fir to keep JavaScript at a minimum.

I am building one. Still a work in progress: https://github.com/adnaan/fir

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