4 ms·
Although I respect that this shouldn't be confused as a standard, as a Go beginner with some very small attempts at creating Go projects[1] I would appreciate s
by whatl3y 7y ago
Although I respect that this shouldn't be confused as a standard, as a Go beginner with some very small attempts at creating Go projects[1] I would appreciate some sort of guidance on organizing code for a larger project. I've considered rewriting some of my larger NodeJS side projects in Go and I, possibly misguidedly, feel like the biggest barrier to entry is understanding the correct way to organize everything (i.e. directory structure). Is there any documentation, tutorials, anything that you or others would recommend for larger Go projects?
[1]
https://github.com/whatl3y/argv https://github.com/whatl3y/argv
https://github.com/whatl3y/cdd https://github.com/whatl3y/cdd
https://github.com/whatl3y/odds https://github.com/whatl3y/odds
- eliben 7y agoI'm curious - what you feel is specifically the barrier? Which parts of your Node project you want to port to Go and don't because you don't know where to put them?