I now had time to review your points extensively: - I agree about the non-stdlib packages and removed direct mention of them while still using them for examples to give a starting point. - Re under-package: I added a comment to clarify to split packages if you're unsure. - The Makefile section was removed due to irrelevance, thank you! - The internal-packages section explicitly mentions to use this if building a cmd. This obviously makes less sense in libraries but I find it useful for cmds. - The explicit go-bindata mention is gone, i still makes deployments easier since you could deploy a single static binary with everything in it. You'd need to gitignore the generated file and make sure it gets built before the binary (go:generate is often a good idea) - what confusion do you mean?
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
