The author, a Go enthusiast with a Java background, argues that Go lacks a full-stack framework comparable to Spring or Quarkus. While Go's philosophy favors simplicity and a pick-and-choose library approach, the author believes the community would benefit from a well-maintained, opinionated framework that balances Go's performance and simplicity with higher-level abstractions. The post contends that such a framework would need corporate backing to be sustainable, and points to Google's Service Weaver as a sign that modular monolith thinking is gaining traction in the Go ecosystem. The author calls on someone — ideally a company — to build this missing piece.
3 Impressions