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.
Go is Google's language, not ours
101–110 of 679 posts
Re: Go is Google's language, not ours
#102The 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.
Re: Go is Google's language, not ours
#103Earlier 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.
Re: Go is Google's language, not ours
#104Earlier 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?
Re: Go is Google's language, not ours
#105I 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.
Re: Go is Google's language, not ours
#106I 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.
Re: Go is Google's language, not ours
#107Haskell 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?
Re: Go is Google's language, not ours
#108Earlier 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.
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
#109This. 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
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
#110Many 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…