[go-nuts] "Selling" Go to Management

2017-05-02 Thread Simon Ritchie
I think interoperability is an important issue. If you are trying to introduce Go into a mature environment you need to avoid any idea that the existing apps will have to be rewritten. For example, gRPC allows a Go application to work with apps written in Java, C#, RoR, Python and a host of

[go-nuts] "Selling" Go to Management

2017-05-01 Thread 'Eric Johnson' via golang-nuts
Just answered a question on Quora today that might be helpful: https://www.quora.com/Why-would-anyone-program-in-Go/answer/Eric-Johnson-157?share=ca0e6b40=zEgo -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and

Re: [go-nuts] "Selling" Go to Management

2017-04-30 Thread Peter Herth
Hi Miki, I would add the following two points: * Module system. This does not only help with the compilation speed, but has a bunch of other advantages. Like clear distinction between public/private data and functions. It also means, you don't have complex makefiles to build your system, the

[go-nuts] "Selling" Go to Management

2017-04-30 Thread Miki Tebeka
Hi, I'm giving a 1 hour talk on Go to mid/high level management. Here are the points I thought to bring up (not in order), I'd appreciate any comments/ideas. * The free lunch is over - threads/async are difficult to work with * Small language - Easy to learn * Simple C based syntax