Live data from Hacker News

Go is Google's language, not ours

utcc.utoronto.ca

101–110 of 679 posts

Re: Go is Google's language, not ours

#101
post #77

Earlier quoted context omitted.

You should use a language based on how well it performs for your problem and domain, and the community around it. Not based on one article or because google is maintaining it.

I think his fear of google's stewardship of the language is the fear of what it'll do to the community around it.

Its incredibly unlikely that Google would take decisions for the language that would make it less effective at what it does.

Re: Go is Google's language, not ours

#102

The article uses "Google" instead of individuals names to make the actions taken seem like sinister actions of a faceless corporation. My interpretation is that Google employs a tight-knit group of people that work on Go and collectively are the BDFLs of the language. This isn't that much different from most large OSS projects, although it does seem likely that this core team weights the opinions of those that they i…

The last two paragraphs of the article address exactly that issue - that it's hard to tell whether the direction of Go development is decided solely by the Go core team or by Google as a corporation.

...was this ever in doubt? i've always thought from day 1 that this is "Go as in made by Google". Even the name branding screams that

Re: Go is Google's language, not ours

#103
post #35

Earlier quoted context omitted.

I'm curious what the distinction is between Rust (driven by Mozilla) and Go (driven by Google).

I had a similar question, but rather, what's the difference between Go with Google deciding what goes in, and Python (a year ago) where the BDFL and a couple core devs decide what go in? Sure you could argue that a company may have different incentives than a BDFL, but in this context, it's not clear that Go would've been more likely to accept the change you're proposing if they weren't being led by Google.

Guido always took the role of gatekeeper and arbiter (I'll consult with the community and decide what submissions go in) rather than a true dictator (I'll decide what goes in... submissions? What submissions?).

Re: Go is Google's language, not ours

#104
post #78
post #67

Earlier quoted context omitted.

You can fork them and become (or remain) irrelevant. Ios development is a walled garden. C# is barely used except to target Windos. Go? Too early to say. If it did fade away, who would miss it, really ? Its express design purpose was to be not powerful enough to make big mistakes in. Has it transcended that? If so, what is its purpose now? Java has shown staying power, despite its shortcomings, although its connectio…

I write software for embedded Linux devices in C# for a living, not exactly targeting Windows now is it?

That use qualifies neatly under "barely".

Re: Go is Google's language, not ours

#105
post #34

I am about to learn a new programming language and I decided against Go just because of this fact. I do not trust Google and reading this article just makes clear how critical the state of the language is in terms of control by the community. Python looks most promising and I already worked with it, but I am not sure yet. Can anyone recommend a viable alternative for Go? Any web-focused language that is performant, m…

If you want performance and garbage collection, Java (and its family), C#, and Go are the major options. I'd pick Go among those every day of the week, but it's not perfect.

By "major options", I guess you mean popular/mainstream options?

Re: Go is Google's language, not ours

#106
post #38
post #34

I am about to learn a new programming language and I decided against Go just because of this fact. I do not trust Google and reading this article just makes clear how critical the state of the language is in terms of control by the community. Python looks most promising and I already worked with it, but I am not sure yet. Can anyone recommend a viable alternative for Go? Any web-focused language that is performant, m…

you shouldn’t let an article decide what language you learn.

How many do you consider enough?

Re: Go is Google's language, not ours

#107
post #92
post #75

Haskell is an excellent example of a community-driven language. It's more mature and advanced than most commercial offerings too, offering a superior type system, fast and efficient executables, lightweight fiber concurrency, software transactional memory, higher-kinded parametric polymorphism and many more features.

Haven’t most of the top Haskell devs been on the Microsoft payroll for years and years?

SPJ is a Microsoft Research Cambridge employee, but as far as I know that doesn't give Microsoft Research (let alone Microsoft itself) any undue influence over the language's direction, they can't gatekeep or ram things into Haskell or GHC.

Re: Go is Google's language, not ours

#108
post #35

Earlier quoted context omitted.

I'm curious what the distinction is between Rust (driven by Mozilla) and Go (driven by Google).

I had a similar question, but rather, what's the difference between Go with Google deciding what goes in, and Python (a year ago) where the BDFL and a couple core devs decide what go in? Sure you could argue that a company may have different incentives than a BDFL, but in this context, it's not clear that Go would've been more likely to accept the change you're proposing if they weren't being led by Google.

I guess the most important distinction is the “B” part (benevolent). Guido is called that because he is known (since before BDFL is a thing) to listen to other people, and adapt when they disagree strongly with his decisions. Google has never demonstrated the same attitude afaict, and in multiple occasions showed exactly the opposite.

Edit: And to answer the question, no, there’s no philosophical differences. And there’s nothing wrong with that. Python never called itself a community’s language (there are instances core devs said in no ambiguous terms that it is Guido’s project). The problem only arises if a project gives an impression that it is owned by the community when it actually isn’t.

Re: Go is Google's language, not ours

#109
post #74
post #6

This. But Go is one in a long line of proprietary languages that those of us who have been around the block know to stay away from. Recently: Java was Sun's, C# is Microsoft's, Swift is Apple's, Go is Google's. With any luck, all will be footnotes in ten years. Those of us who knew better than to get invested in them will be fine. Everyone else gets a chance to learn something.

> With any luck, all will be footnotes in ten years. Java and C# are not going anywhere, especially now that .NET works on OSX and Linux. Swift, unlikely. Go, still uncertain. It's fairly short-sighted to criticize a language and hope it dies out in usage just because a corporation is chiefly responsible for it. [0]: https://dotnetfoundation.org/about

Swift has garnered little traction outside iOS development, while other languages are gaining traction inside iOS development (javascript mostly, but Kotlin is also trying to make headway into iOS development).

I won't put survival rating for it to be very big. I'm sure Apple would keep it for decades to come, but I'm wouldn't bet on it being anywhere near as popular as it is now in the future.

Re: Go is Google's language, not ours

#110
post #17

Many like Go because it is an opinionated language. I'm not sure that a 'community' run language will create something like that because there are too many opinions. Many claim to represent the community, but not the community that doesn't share their opinion. Without clear leaders I fear technical direction and taste will be about politics which seems more uncertain/risky. I like that there is a tight cohesive group…

My thoughts exactly! It's important to have a community and to work with it, but, especially for a programming language, there has to be a clear concept of which features should be implemented and which not - just accepting community contributions for the sake of making the community feel good would be the wrong way. Otherwise you end up with a feature monster like innumerable other programming languages, and that's exactly what Go doesn't want to be.
Post reply on HN