+Automatically deciding what's important in a program's dependencies is not easy.
+Thanks
+Yes, one could, and that would be a stylistic decision.
+Best not to promote the bad idea.
+Nil means nothing.
+People often spend too much time worrying about the things that don't matter.
+Often the reason something was done is more important than what was done.
+I believe this is not a Go issue.
+Are you running Xcode 8.3?
+I don't think so.
+Yup.
+Code comments can be helpful with unusual situations like this.
+The key word is simple.
+If I could, I would disallow it altogether.
+I completely disagree.
+I say leave it alone.
+I wasn't speaking metaphorically.
+A nil map is like a regular map but it has nothing in it, cannot grow, and takes zero space.
+We live in a digital dark age.
+Neither of your issues is a problem.
+Your ideas may make people happy, which is not a small thing, but do they really help?
+What's this? https://plan9.io/
+Consistency is a better explanation.
+Code can move.
+You might find blog.golang.org/constants helpful.
+Over time, everything gets better but also worse and always bigger and more complex.
+Nice to see Egreg again.
+It wasn't my intention.
+The Blit was nice.