It should always be 'use the best tool for the job'. If Go seems like a good fit for a task, use it. We've used Go for creating web services accessed via restful API's and it works great. I've personally used Go to create command line utilities to help with development. We've also used it to prototype systems before using other languages.
We don't see it as a risk but as a competitive advantage. On Monday, 19 December 2016 13:03:43 UTC, Tieson Molly wrote: > > What arguments or factors have contributed to your company adopting Go? > > Many businesses see switching to a new language or even using a new > language side by side with their existing language choice as a business > risk. > > Best regards, > > Ty > > > -- 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.
