On Thu, Jan 25, 2018 at 01:26:00PM -0800, Florin Pățan wrote: > I'm not saying that we should be against recommending the standard library, > by all means, it's one of the best assets of the language. But maybe it's > time we should think about saying: Start with this framework, insert > framework name here, and then, as you gain more Go knowledge, or you are > curious about how it's done, look into these packages, insert collection of > packages here, and finally, do not discount the standard library, as it is > very powerful and it can do a lot out of the box without introducing > further dependencies into your code.
We're talking about a beginning Go programmer that has yet to learn how some of the more advanced parts of the language fit together properly. Now, assuming that actually understanding your program is a goal (in contrast to just bashing things together until they appear to do what you want), importing a huge and complex framework doesn't seem very helpful to me, for the same reasons you start learning programming with "Hello, world!" and not by extending a distributed database engine. -- 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. For more options, visit https://groups.google.com/d/optout.
