4 ms·
Re "go new": I think part of the problem with that is that people have quite different ideas of what a good project structure is. It also varies a lot between a
by benhoyt 6y ago
Re "go new": I think part of the problem with that is that people have quite different ideas of what a good project structure is. It also varies a lot between a simple CLI tool (for which main.go and maybe go.mod is enough) and a large multi-package server project.
Can you explain what you mean by "bizarre Makefiles"? I've never used Makefiles for my (admittedly fairly small) Go projects, because "go build" just works.
- hactually 6y agoI've seen a number of projects where the root directory is a load of other folders and then there's a Makefile and it's a kafkaesque nightmare. I agree on the toplevel `main.go` vs the `./cmd/myapp/main.go` style needing catering for that only comes out as the project evolves... maybe it should be a go vet addition instead :D
- stubish 6y agoGo modules are removing the need for much of the Makefile magic. You still have use of a Makefile if you need vendoring or are dealing with non-public branches, but things can be much simpler.