Does Go have a full-stack framework like Laravel, and if so, which one is the most popular, or Top-3?

Question

go

I want to get acquainted with Golang in practice, and I want to start right away with some popular framework, hence the question:
- Which one is better to start with?
1. The closest to me is something like Laravel, i.e. full-stack with router, controllers and template engine. Is there such a thing? Which one is the most popular with a developed eco-environment and a bunch of step-by-step tutorials? )) Well, or if there is a top three - what is it?
2. As an option - a Go framework for writing native Android applications?
3. Or if there is neither one nor the other - at least for the REST API some kind of developed framework.
Thank you.

Answer 1

yes, but they are not
needed

Answer 2

Strange, no one mentioned gorilla https://www.gorillatoolkit.org/ It is a library, not a framework, and a modular library that does not impose an architecture. Using frameworks is generally frowned upon by the community, not idiomatic, and gorilla was considered the industry standard. The gorilla router/multiplexer is fully compatible with the standard library router, which guarantees that middleware that supports the standard library architecture will work. The websocket module https://www.gorillatoolkit.org/pkg/websocket does not seem to have any worthy alternatives yet.

Answer 3

Well, straight from the most out-of-the-box probably Hugo . The rest, like gin and others like it, are rather toolkits than frameworks. But comfortable, no doubt.
In general, it is customary to use microframeworks in Go, that is, to assemble the necessary product from them, taking only what is needed, and not pulling millions of lines of code into the project for the sake of just routing, as is customary, for example, in python using Django as an example.
Whether this is good or bad is an open question, but you need to understand this when starting to write a website in Go.
And so in the standard lib there are html templates, you can write using them, and generally do without frameworks.