go-callvis VS golang-standards/project-layout

Dependency plugins and tools are automatically installed after executing the command: protoc-gen-go, protoc-gen-go-grpc, protoc-gen-validate, protoc-gen-gotag, protoc-gen-go-gin, protoc-gen-go-rpc-tmpl, protoc-gen-openapiv2, protoc-gen-doc, golangci-lint, swag, go-callvis.

When designing a Go project, look to real-world examples like Kubernetes, Vault and the Golang Standards Project Layout. These showcase how powerful Go can be when the architecture embraces simplicity over rigid structure. Rather than trying to make Go fit a Clean Architecture mold, embrace an architecture that’s as straightforward and efficient as Go itself. This way, you’re building a codebase that’s not only idiomatic but one that’s easier to understand, maintain, and scale.

https://dev.to/booscaaa/implementando-clean-architecture-com-golang-4n0a https://github.com/golang-standards/project-layout https://blog.boot.dev/golang/golang-project-structure/ https://github.com/bnkamalesh/goapp https://www.wolfe.id.au/2020/03/10/how-do-i-structure-my-go-project/ https://blog.logrocket.com/flat-structure-vs-layered-architecture-structuring-your-go-app/ https://developer20.com/how-to-structure-go-code/ https://dev.to/jinxankit/go-project-structure-and-guidelines-4ccm https://github.com/bxcodec/go-clean-arch https://golangexample.com/example-go-clean-architecture-folder-pattern/ https://www.calhoun.io/flat-application-structure/ https://go.dev/doc/effective_go#names https://go.dev/blog/package-names

cmd: here where we will leave the main.go that starts our app.

> https://github.com/golang-standards/project-layout

The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether so now no one can see it.

Even when it would not have such parasitic name, many seasoned Go programmers, me included, consider the self-proclaimed "Standard Go project Layout" as the opposite of what is good and advisable.

Unfortunately, the name just works, so it is being recommended all over the Internet since its inception.

Your comment makes it look as if you're saying you hate the Go development team, but it seems that isn't the case.

I get a little of what you're saying, I wouldn't say I hate anyone, but I strongly dislike how a lot of projects are organized. I think a lot stems from https://github.com/golang-standards/project-layout , which pretended to be standard and was so (ab)used one of the creators opened an issue about it. If you look at the actual Go src, it's much, much cleaner.

So you don't get blind sided for self proclaimed "standards" that are not