golang-standards/project-layout VS cookiecutter-golang

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

I am writing a project that has two components: a CLI and a library. I've organised the project as follows (as per organisation instructions):

Familiarity with the standard Golang project structure, which you can find here.

I've been learning how to build web applications using different frameworks and languages for a while now, such as Laravel with its MVC architecture and Node.js following the 'Hapi.js Way'. As I'm trying to create a new portfolio project using Go, I found myself contemplating over the ideal project structure. I wanted something that not only aligns with the standard Go project layout, but also makes the code both easy to write and understand. That's when I stumbled upon the concept of Hexagonal Architecture, as showcased in Netflix's engineering blog. The idea of seamlessly swapping infrastructures with minimal code changes fascinated me, and I decided to implement it in my new project.

~ cookiecutter https://github.com/lacion/cookiecutter-golang.git full_name [Luis Morales]: Ricardo Castro github_username [lacion]: mccricardo app_name [mygolangproject]: demo project_short_description [A Golang project.]: A demo docker_hub_username [lacion]: mccricardo docker_image [lacion/alpine-base-image:latest]: golang:1.16.5-apline3.14 docker_build_image [lacion/alpine-golang-buildimage]: golang:1.16.5-apline3.14 Select docker_build_image_version: 1 - 1.13 2 - 1.12.9 3 - 1.11.9 Choose from 1, 2, 3 [1]: 1 Select go_mod_or_dep: 1 - mod 2 - dep Choose from 1, 2 [1]: 1 use_docker [y]: y use_git [y]: y use_logrus_logging [y]: y use_viper_config [y]: y use_cobra_cmd [y]: y Select use_ci: 1 - travis 2 - circle 3 - none Choose from 1, 2, 3 [1]: 3 Initialized empty Git repository in /home/mccricardo/test/demo/.git/ [master (root-commit) 2e82ac9] Initial Commit. 13 files changed, 597 insertions(+) create mode 100644 .gitignore create mode 100644 AUTHORS.md create mode 100644 CONTRIBUTING.md create mode 100644 Dockerfile create mode 100644 Makefile create mode 100644 README.md create mode 100644 cmd/root.go create mode 100644 cmd/version.go create mode 100644 config/config.go create mode 100644 go.mod create mode 100644 log/log.go create mode 100644 main.go create mode 100644 version/version.go

@backstage/plugin-scaffolder-backend through CookieCutter "knows" how to bootstrap Golang projects based on cookiecutter-golang. And that's how all the magic happens.