Earlier quoted context omitted.
Zero drama is easy when you get paid (a lot) to work on something.
Huhhh? Have you ever worked at a large enough company where stakeholder interests are not aligned?
Russ Cox is stepping down as the Go tech lead
41–50 of 396 posts
Re: Russ Cox is stepping down as the Go tech lead
#42Earlier quoted context omitted.
Zero drama is easy when you get paid (a lot) to work on something.
That’s unfair. There’s plenty of drama in projects with all sorts of funding situations. Look at eg Rust. Lots of drama and it’s anyone’s guess if the code you wrote a year ago would work today.
Is that true? In what sense? I was under the impression the editions took care of that.
Re: Russ Cox is stepping down as the Go tech lead
#43Re: Russ Cox is stepping down as the Go tech lead
#44Earlier quoted context omitted.
> I'd also like to see less google control of the project. What does this even mean? Google basically just finances the project, but doesn't really "control" anything, never mind that "Google" isn't a monolithic entity in the first place.
They could be a non-google employee. They could let the community vote on who new leaders are, etc...
Who is "they"? Who is "the community"? Who qualifies for a vote and who doesn't? I never contributed any code to the Go compiler or stdlib, but have contributed to some aspects of the "wider ecosystem", including some things that see fairly broad usage, and am (coincidentally) wearing a 2018 GopherCon t-shirt as I write this. Do I qualify? Does someone who has been writing Go for a year qualify? A week? Someone who never even wrote Go code? Someone who sent in a single patch to stdlib? And how do you verify all this?
Saying "let the community vote" is easy, but if you think about it for more than a second you will realize there's tons of difficulties and that it doesn't really work. I also don't really know of any project that works like this: it's pretty always a fairly small group of "core contributors" that get to decide.
Re: Russ Cox is stepping down as the Go tech lead
#45Out of interest, why are people so confident in Google when it comes to Go, yet every other day there's articles about how Google can't be trusted in related to Dart/Flutter which are soon to be abandoned?
Re: Russ Cox is stepping down as the Go tech lead
#46I think the only reason I used go at some point was because of Russ Cox. Have joined the dark side and switched to rust ;). Wonder what he’s going to do next? Maybe just moving around within G? or another OSS project within G?
Re: Russ Cox is stepping down as the Go tech lead
#47Earlier quoted context omitted.
That’s unfair. There’s plenty of drama in projects with all sorts of funding situations. Look at eg Rust. Lots of drama and it’s anyone’s guess if the code you wrote a year ago would work today.
> It's anyone's guess if the code you wrote a year ago would work today Is that true? In what sense? I was under the impression the editions took care of that.
Re: Russ Cox is stepping down as the Go tech lead
#48Earlier quoted context omitted.
Almost zero drama and almost no feature creep or breaking changes. The team seems to have a focus, and does not change it easily. That is important for a programming language, and it doesn’t happen organically.
Zero drama is easy when you get paid (a lot) to work on something.
Re: Russ Cox is stepping down as the Go tech lead
#49RSC has a really good blog: https://research.swtch.com/
Re: Russ Cox is stepping down as the Go tech lead
#50Out of interest, why are people so confident in Google when it comes to Go, yet every other day there's articles about how Google can't be trusted in related to Dart/Flutter which are soon to be abandoned?
source?