pushup
Pushup is for making modern, page-oriented web apps in Go (by adhocteam)
yaegi-template
Use yaegi as a template engine. (by Eun)
| pushup | yaegi-template | |
|---|---|---|
| 17 | 5 | |
| 832 | 31 | |
| 0.4% | - | |
| 6.6 | 0.0 | |
| 14 days ago | 11 months ago | |
| Go | Go | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pushup
Posts with mentions or reviews of pushup.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-09.
-
Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
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.
-
Pushup Offers Speed of Go in Web Development Framework
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...
- Golang tech stack
- Best front-end stack for Golang backend
- Pushup – A server-side, page-oriented web framework for Go
- Pushup: a new compiler for making web apps in Go
- Pushup: a new compiler for building web apps in go
- First public release of Pushup: a new compiler for making web apps in Go
yaegi-template
Posts with mentions or reviews of yaegi-template.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-04.
- First public release of Pushup: a new compiler for making web apps in Go
-
runzmd: Runnable Markdown for Tutorials and Demos
I experimented with this as well: https://github.com/Eun/yaegi-template/tree/master/examples/evaluate_readme
- What I'd like to see in Go 2.0
-
Frontend components with Golang
I always found the go templating too limited. I personally use yaegi for this: https://github.com/Eun/yaegi-template