Go web developers assemble common app features themselves
Go developers want to build web applications with less setup, but report having to assemble or implement basics such as database migrations, CRUD, templates, and asset bundling themselves. Some also want a lightweight backend that keeps database access behind server-side APIs, rather than a workflow centered on direct client-to-database access. The signals point to demand for a more integrated, Rails-like Go workflow, though they do not establish how many developers would pay for one.
For go web application developers. Mentioned from Apr 2019 to May 2026 on Bluesky, GitHub and Hacker News.
7 different people described this problem in 7 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.0/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Golang for monolithic web-app that has to handle db migration (yeah I know something exist), implement multiple crud objects (remember, Golang microservices typically has smaller context and challenges than a medium size web-app) is pain in the ass!
hello_moto on Hacker NewsDec 2023I’d love to find something in Go or Typescript that made me feel quite as productive as Rails did
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks