Choosing a Go stack
Long-form answers to the decisions a Go team actually faces, written to be useful whether or not you end up using Grit. Every project mentioned is checked against its own source, and the ones that have gone quiet are named as such.
Full-stack frameworks for Go
Go has no Rails, and the phrase means three different things. Buffalo, Beego, Bud, templ with HTMX, Encore, PocketBase and Grit, compared.
12 min read
Go web frameworks: net/http, Chi, Gin, Echo and Fiber
Four of the five are routers, not frameworks. Where that line falls, and the list of things none of them give you.
10 min read
Admin panels for Go
Why Go has no Filament, the four ways teams solve it, and the question that decides between them: where your schema lives.
9 min read
A Go backend with a React frontend
The four problems the tutorials skip: type drift, auth across two origins, the dev proxy, and one artefact or two.
9 min read
Coming to Go from Laravel
Every part of Laravel mapped to its nearest Go equivalent, including the four gaps with no good answer.
8 min read
CRUD and scaffolding generators for Go
sqlc, ent, GORM gen, goa and full-stack scaffolders. What each writes, and what it leaves you.
8 min read
Looking for a direct comparison?
These guides are about the decision. If you already know the two things you are choosing between, the side-by-side pages are more direct.
Grit compared to nine alternatives