Re:Go performance from version 1.2 to 1.18
by oefrha on Friday February 04, 2022 @03:10AM
(#30204111)
Compared to say Rails/Django, there’s very little magic in the Go ecosystem. You end up rewriting a lot of boilerplate. People would often recommend that you start with bare bones net/http, database/sql, etc., not even a minimal framework like Gin/Echo. This is okay for building performant microservices, but it does get annoying when you’re just trying to spin up your twentieth boring CRUD backend quickly.
[ Parent
| on HN ]
Re:Go performance from version 1.2 to 1.18
by tompston on Friday February 04, 2022 @05:57AM
(#30205261)
I wrote a REST API / boilerplate reducing codegen tool for this exact reason for the Go Fiber framework. Maybe might help.
Re:Go performance from version 1.2 to 1.18
by kamalhm on Tuesday February 08, 2022 @08:36AM
(#30258178)
as someone not familiar with Go, always wondering why Go people like to recommend the net/http package instead of those framework, are most go backend services actually written from scratch? I find it quite hard to understand since in the Java world it's usually SpringBoot everywhere