Our great sponsors
-
It is also worth mentioning newly published "style guide" from Google. Which is mainly a compilation of Effective Go and Code Review Comments.
-
The layout itself is bloated and unnecessary IMO, regardless of the size of the project. It's a good example of what to avoid in Go for that reason, as well as those pointed out by Russ Cox.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Here's a repository with anti-pattern examples dedicated to web apps. It comes with blog posts describing them. https://github.com/ThreeDotsLabs/go-web-app-antipatterns
-
sarama
Discontinued Sarama is a Go library for Apache Kafka. [Moved to: https://github.com/IBM/sarama]
Well, as someone who reviews a lot of code, I don't like seeing 100s of little files when a handful of logically grouped files would do. For example, this popular go project: https://github.com/Shopify/sarama is currently 256 small .go files, largely following a one class/file rule.