News for hackers. Stuff that matters.
Re:Proposal: Go should have generics by pjmlp on Thursday April 14, 2016 @08:30AM (#11496059)
Go is thriving because it is Google sponsored.

If it came from "Joe the dev" no one at HN would give it a second look.

Re:Proposal: Go should have generics by zellyn on Thursday April 14, 2016 @08:44AM (#11496142)
I simply do not believe this.

I believe it is thriving because it was well-designed, by extremely influential individuals, and the early library work was stellar. Also, several other experienced and influential programmers tried it, and expressed something along the lines of "programming is fun again!"

Inside Google, the two main programming languages are C++ and Java, not Go (at least when I left, in September). The Go tooling is generally less capable, but the interfaces smaller, and often nicer: they have the dual benefits of hindsight, and a small but very smart team that really cares about conciseness and clean APIs.

Of course, it's undeniable that the Google name helps a bit. And paying a team of very experienced (and presumably very expensive) developers to work on it makes a huge difference. But I think it would be as successful if those same developers were sponsored by Redhat, or Apple, or just about anyone.

Re:Proposal: Go should have generics by Scarbutt on Thursday April 14, 2016 @01:17PM (#11498605)
Redhat or Apple are not "Joe the dev" though
Re:Proposal: Go should have generics by imtringued on Thursday April 14, 2016 @01:54PM (#11498969)
Java Joe works at Readhat though :P
Re:Proposal: Go should have generics by coltonv on Thursday April 14, 2016 @10:11AM (#11496833)
Dart is also Google sponsored and no one uses it despite the fact that it's actually a pretty great general purpose language. People use go because it's productive and had a PHENOMENAL standard library for networking.
Re:Proposal: Go should have generics by waimbes on Thursday April 14, 2016 @11:23AM (#11497416)
> Dart is also Google sponsored and no one uses it despite the fact that it's actually a pretty great general purpose language.

Citing an example that had support from Google and failed does not refute the claim that Go would have failed if not for Google's support.

Re:Proposal: Go should have generics by myg204 on Thursday April 14, 2016 @12:24PM (#11498018)
It clarifies the fact that Go is successful for more reasons than just being pushed by Google. So it focuses the question to "what is it that people like about it". And then we can have a better conversation.
Re:Proposal: Go should have generics by pjmlp on Thursday April 14, 2016 @10:35AM (#11497054)
Given that .NET and Java already had a PHENOMENAL standard library for networking by the time Go came out, I really bet in the Google bias.
Re:Proposal: Go should have generics by narrowrail on Thursday April 14, 2016 @11:02AM (#11497255)
Your theory fails to account for the lack of success with respect to Dart; so, it seems more like something you have an urge to believe (despite a lack of evidence).
Re:Proposal: Go should have generics by pjmlp on Thursday April 14, 2016 @06:42PM (#11500860)
Dart has been abandoned by Google the day that Angular team has chosen Typescript instead of believing in Dart, thus sending to the world the message that the company doesn't believe in it.

Whereas there are a few production examples of Go at Google.

Re:Proposal: Go should have generics by narrowrail on Thursday April 14, 2016 @10:56PM (#11501780)
My understanding is that Dart is used by Google Fiber for their routers, so I wouldn't call that abandoned yet. But, the point is that Google supporting a language does not seem to imply its eventual success.
Re:Proposal: Go should have generics by spankalee on Friday April 15, 2016 @01:36PM (#11506162)
That's some odd reasoning. The Angular team does not decide which languages are invested in by Google.
Re:Proposal: Go should have generics by pjmlp on Sunday April 17, 2016 @02:29AM (#11513720)
No, but Google decides what their employees are allowed to use.

In this case a company team was allowed to use a competing language instead of the one designed in-house for the same purpose.