This topic has been discussed many times on this list. Do a search and you'll see a lot of great points.
My opinion is that you should use the standard library, and only reach for individual components when it would provide a significant advantage. Do not use any "framework." Like Go's object-oriented design which affords embedding and not inheritance, you should plug in components as necessary to your code. Don't write your code to conform to the opinions of a framework. For example, if you want to use a plugin for websockets, sessions, or routing, that's fine. But don't look for a Django/Rails replacement. -- 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.
