Re:Ask HN: What is the current state of web frameworks in Go...
by everdev on Friday July 13, 2018 @11:45PM
(#17528684)
The common reply in the Go community is "don't use a framework" or "roll your own".
The idea is that small packages suited to individual tasks are a better solution than a large framework package that includes more than you need, or tried to for your use case into a shared, common use case.
IMO, frameworks are great for rapid prototyping, but in Go and it's explicit programming style, most devs prefer to build most by have and only import a minimal number of packages for specific tasks.
Re:Ask HN: What is the current state of web frameworks in Go...
by bigdubs on Thursday July 19, 2018 @09:31PM
(#17571796)
Some common helpers are nice though, not sure that constitutes a framework but it definitely saves time not having to rewrite response compression and logging.
The idea is that small packages suited to individual tasks are a better solution than a large framework package that includes more than you need, or tried to for your use case into a shared, common use case.
IMO, frameworks are great for rapid prototyping, but in Go and it's explicit programming style, most devs prefer to build most by have and only import a minimal number of packages for specific tasks.