Why it's worth learning Go

Re:Why it's worth learning Go by pacala on Saturday September 15, 2018 @06:42PM (#17996369)

Go was designed for data munging via gRPC.

[ Parent | on HN ]

Re:Why it's worth learning Go by village-idiot on Saturday September 15, 2018 @09:38PM (#17996918)

One of the clear design needs for go was “you have a crap ton of code you need to write, and you need to aggressively parallelize the work over a bunch of mixed skill devs, without the worst ones fucking it up, and without the best going off the reservation and making something that can’t be understood later.”

Personally that sounds like my own hell, but that’s the world Google lives in.

[ Parent | on HN ]

Re:Why it's worth learning Go by erik_seaberg on Saturday September 15, 2018 @11:02PM (#17997106)

Despite Pike's appalling contempt in https://talks.golang.org/2012/splash.article I'm not convinced this is a problem Google actually has. They're faced with perverse incentives but they're far from stupid.

[ Parent | on HN ]

Re:Why it's worth learning Go by village-idiot on Sunday September 16, 2018 @02:48AM (#17997632)

Pike’s attitude has been a large factor in me not bothering with Go.

[ Parent | on HN ]

Re:Why it's worth learning Go by andresp on Monday September 17, 2018 @02:13PM (#18008405)

Maybe with the exception of the old JS callback hell I have never seen any other language deteriorate code into spaghetti projects more quickly than Go with channel and duck typing abuses.

I think if it does a very poor at keeping "the worst ones" from "fucking it up".

[ Parent | on HN ]