While writing this blog and leading Go teams for a couple of years, the most common question I heard from beginners was “What framework should I use?”. One of the worst things you can do in Go is follow an approach from other programming languages.
Other languages have established, “default” frameworks. Java has Spring, Python has Django and Flask, Ruby has Rails, C# has ASP.NET, Node has Express, and PHP has Symfony and Laravel.

ThreeDotsLabs' platform is  dedicated to providing insights and resources for software engineers and technology enthusiasts. Through articles, tutorials, and open-source projects, ThreeDotsLabs offers insights into software development best practices, design patterns, and emerging technologies. Developers can learn about building scalable architectures, microservices, and cloud-native applications to solve real-world problems effectively.

Three Dots Labs

Go is built around the Unix philosophy that says: Write programs that do one thing and do it well. This philosophy originated from Ken Thompson, the designer of the B programming language (a precursor of C) and also… Go! The best examples are the most widespread interfaces: the and the.

The Best Go framework: no framework?

The alternative? Building services without a framework

Totally agree 👌 What I found works best for me is to read through one or two frameworks to learn their implementation architecture and then build a very minimalistic version that works best for me! This way I apply the best practices and manage it in-house without creating any dependencies to external frameworks 👍

The definition of a framework is a bit broad. Maybe when you think of framework you think about what other languages have like Django for Python or Spring for Java.
However inevitable people create framework and propose abstraction to simplify things.
I would be interesting to clear thing us and define what is a framework and what is a library.
A framework:
Provide an abstraction
providing generic functionality
Becomes a first-class citizen in you application (you build around it
A library:
Provide concrete implementation(s) to perform an actions
The author for instance created a framework called watermill to help people manage event in Go application.
<blockquote>
Go developer don’t like framework, but Go developers write frameworks
</blockquote>