4 ms·

Questions left unanswered: - When are go multi-module workspaces best used? - What should you use for the module-path argument to `go mod init` if you don't e

by js2 3y ago

Questions left unanswered: - When are go multi-module workspaces best used? - What should you use for the module-path argument to `go mod init` if you don't ever intend to share the repo or you don't yet know where you will be sharing it?

arp242 3y ago
1. When it's more convenient than not using them. 2. Anything is fine: just a name ("myproject"), a fake URL, a real URL. Whatever works for you. This may seem overly simplistic and I'm not trying to be dismissive, but that's really what it comes down to. Sometimes things really are just simple. I don't understand the desire to "standardize" and "document" everything to the microscopic detail.
pjmlp 3y ago
Another one, - How to handle binary modules?
- domust 3y ago
  Just don't: https://github.com/golang/go/issues/28146 https://github.com/golang/go/issues/28146
  - pjmlp 3y ago
    I know, yet another thing that makes Go unusable for typical corporations.
    - Cthulhu_ 3y ago
      How come said typical corporations need binary modules? Those aren't very portable, and make maintenance long term a lot more complicated.