Hacker News Reader

Comment by commitpizza | Hacker News Reader

The only reason why I would never use Go is because it is made of and controlled by Google.

Maybe that is a stupid reason but I stand by it.

That's not stupid, that's wise. Go is designed by Google to solve Google technology and employment problems. There's an underlying philosophy that you buy into when you pick a language. Open languages will be upfront about their worldview. Go's raison d'être is more or less "make programmers expendable like soldiers on the front" but of course they never spell it out like that. They only market it out because they need a pool of fresh warm bodies to throw at their Google problems.

I wrote more Go programs that I can remember.

I never worked at Google and presumably I don't have Google's problems and yet Go is the best language I found to wrote those programs. Simple, fast and productive.

Could you connect the dots for me: what exactly is that Google needs that I don't and how does that map to design of Go?

Is it compiled because only Google needs statically compiled, easily cross-compilable, easy to distribute executables?

Is it portable to almost every OS / arch available because that's something only Google needs?

Is it statically typed because only Google cares about catching type errors at compilation time?

Is it garbage collected because only Google cares about the productivity and memory safety of programs?

Which Go design features solve problems that only Google has?

Currently googles problems might map well with your problems. The issue (and fear) is what if google's problems change in the future and don't line up with yours?

Reply on news.ycombinator.com