On 1/12/21 9:43 AM, Axel Wagner wrote: > git init > go mod init <module-path> > > I guess you *could* safe the `git init` part, but is that really worth the > added > complexity?
Sorry I meant replace keyword, not require in the original mail. Though requiring a domain name is equally unintuitive. I guess the point is that a domain is good for one scenario and env variables shouldn't need editing for GoPATH. If env editing isn't needed for go path then they should be put on an equal footing, maybe GoPATH put back in primary position. I've never really used GoPATH much but I'm not sure a vendor folder should be required. I usually init git from within vscode afterwards. I wonder if doing it pre would save me any trouble. AFAICT go mod init works great, if you use remote git. If you work locally then you have to manually edit the .mod files. For me with a replace directive to bring in general libraries. That is the likely scenario of a new user. I have noticed that GoPATH is more prominent again in the docs. Generelly Gos docs and methods are far simpler and better than Dart/Flutters but in this regard. Flutter create followed by opening the folder in an IDE with import files as required, is a lot simpler. I believe they may have some complex cyclic dependency checking though. > FTR, I don't think what you are trying to solve here is a problem Jaana is > having. True, but I think maybe more pertinent to the issue of onboarding. After all if you are using Kubernetes, then you aren't exactly opting for simplicity anyway. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/930e33cd-be9d-c2d7-bc8c-ffa84e66e234%40gmail.com.
