Go web frameworks

[turbid pagoda]

Hi,
Why do we have to choose between frameworks like gin, fiber or iris for develop web applications? Wouldn't it be better if it was an official framework? I researched which of these to choose, but I was really undecided. Golang docs use gin but most developers recommend fiber. Of course there are a few other options like iris.

[glass oak]

I recommend Gin.

The framework is very good.

I love Gin.

Gitea uses go-Macaron.

Of course, Macaron is less known, but one of the successful projects called Grafana was built by go-Macaron.

So It's up to you.

[kindred yoke]

check this faq
#1025280887388127272 https://canary.discord.com/channels/118456055842734083/1025280887388127272
do you really need a framework?

[turbid pagoda]

Yes I read this faq. I actually like not to use frameworks. But the use of the framework is too much to be underestimated. If net/http is sufficient, why do many projects use frameworks? Is there any possibility of needing a framework when developing with net/http in a project?

Thank you for answer. @glass oak

[carmine tulip]

net/http is sufficient for a fair bit, for all else it’s usually (in my experience) better to get a library that does the thing you want rather than a whole framework

[kindred yoke]

If net/http is sufficient, why do many projects use frameworks?
i feel like that's not the best reasoning you could have brought out to support something,
it's pretty much in line of "everyone is doing it, so i should follow suit"
without fully understanding why it make sense for their usecase, but simply assuming they are correct

Is there any possibility of needing a framework when developing with net/http in a project?
like jonno said, generally we prefer modular approach, need something? bring a library
instead of a full blown framework, we bring in only what we need to get our job done

[turbid pagoda]

you're right, instead of the approach of "everyone is doing it, so i should follow suit", I am curious about why a framework is needed if "net/http" is sufficient.

the modular approach sounds good. it made so much sense to me
thank you for your answers. @carmine tulip @kindred yoke

[bleak timber]

Fiber would be the worst pick. It's not compatible with the standard library. The net/http, as others have said, is essentially the official way of working with http. If you want to have more tools, like route grouping, middlewares, etc you could look at go-chi.

[turbid pagoda]

ty for your suggestion