Comment by v5v3
2 days ago
Yes but it is still controlled by Google and has not been moved to a foundation? Like for example the Rust Foundation.
2 days ago
Yes but it is still controlled by Google and has not been moved to a foundation? Like for example the Rust Foundation.
True. However the control really only extends to the name and the amount of human effort allowed by employees on the Google implementation, as far as I can tell.
If Google decide that they were no longer developing their implementation of the language and moving the employees to other things, there's nothing stopping a foundation from being established. It would be ideal if this was organised by Google as part of their exit, but failing that I would expect other stake-holders in the language to organise something.
What advantages would moving to a foundation like structure bring to Go?
Strategic direction, roadmap and general decisions are set by the independent foundation and not by Google.
Okay. So it's really just a protection against Google deciding to stop its own development and leaving everyone hanging. That's good. I could get on board with that.
For me however, I think it would be a challenge for the foundation to maintain the slow-and-steady development that we've seen under Google.
To bring it back to the main topic: I think a language that rarely introduces major new features, is good for teaching purposes. From that perspective, I think Go is a good language for teaching core concepts.
Controlled in the sense that most of the maintainers are Google employees. But how does that make a difference? The tool chain is available as FOSS, there’s no possibility of a rug pull.
All of the same things were always true, and are true today, of Java. You can use Java entirely without touching anything Oracle-tainted. And yet, here we are.
Not to mention, nothing stops Google from deciding tomorrow to stop distributing any Go code freely. They pull the public repos, pull the public docs, pull the package server and cache, everything. They release everything back only under proprietary licenses: it's their code, they can change the license at any time.
Sure, you could still use anything they released yesterday, if you still have a copy. But would anyone feel that is a sound business or even personal decision?
I'm not saying in any way that I expect Google would do this. I'm just pointing out that this is 100% within their legal rights to do, and under their ability. I think Google is quite trustworthy on this, but if you feel they are not, you should be aware that the license doesn't act as any kind of real shield.
realistically no chance of a rug pull of course.
But my philosophy is about libre, in the context of an educational institution. Teaching java was a mistake, and it would be the same to do so with golang for the same reasons. Students should be learning the concept embedded in the language, rather than the commercial ecosystem associated with the language.