Live data from Hacker News

Russ Cox is stepping down as the Go tech lead

groups.google.com

31–40 of 396 posts

Re: Russ Cox is stepping down as the Go tech lead

#31
post #17

Earlier quoted context omitted.

> I'd also like to see less google control of the project. That doesn't look like is going to happen — the leadership change announced here seems to me to continue on the Google path. Both Austin and Cherry are relatively unknown outside Google and are to my knowledge not active in the community outside Google.

> Both Austin and Cherry are relatively unknown outside Google and are to my knowledge not active in the community outside Google. I don't believe this is true at all. They are both highly active in external Go development, far more active than I have been these past few years. (It's true that neither gives talks or blogs as much as I do.)

I understand and respect your perspective on Austin and Cherry’s involvement in the Go community. Their contributions may indeed be less visible but still impactful. However, the community’s perception of leadership is crucial, and visibility plays a big part in that. For instance your long form blog adds context to decisions you’ve taken in the past. I hope their active roles will become more apparent, fostering a stronger connection with the broader Go community.

Re: Russ Cox is stepping down as the Go tech lead

#32
post #2

Thank you, rsc, for all your work. Development in Go has become much more enjoyable in these 12 years: race detector, standardized error wrapping, modules, generics, toolchain updates, and so on. And while there are still things to be desired (sum types, better enum/range types, immutability, and non-nilness in my personal wishlist), Go is still the most enjoyable ecosystem I've ever developed in.

Nomination for RSC's greatest technical contribution: module versioning. Absolutely fundamental to the language ecosystem. https://research.swtch.com/vgo-intro

Agreed, see the index of those posts: https://research.swtch.com/vgo

Other contenders I find myself sharing and re-reading:

- https://swtch.com/~rsc/regexp/regexp1.html

- https://swtch.com/~rsc/regexp/regexp4.html

- https://research.swtch.com/bisect

- https://research.swtch.com/zip

Re: Russ Cox is stepping down as the Go tech lead

#33
post #25
post #23

Earlier 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.

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.

Re: Russ Cox is stepping down as the Go tech lead

#35
post #25
post #23

Earlier 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.

And yet we've had lots of drama in Linux and Redhat mailing lists, involving people paid to work on the respective projects, and using their work email.

Re: Russ Cox is stepping down as the Go tech lead

#39
post #25
post #23

Earlier 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.

I would rather say that it is easy to have zero drama when most of the committers come from a single large companies.

Re: Russ Cox is stepping down as the Go tech lead

#40
post #28

Huge news! I hope the new leadership remembers that keeping golang small and simple was its greatest strength. Adding generics was too much, and while I think there are some important small cases when it's valuable, in practice people are using it when they shouldn't. I'd also like to see less google control of the project. I'm certainly thankful for golang as it made my https://github.com/purpleidea/mgmt/ project po…

> Adding generics was too much I strongly disagree. Sure, like anything in programming, generics can be misused. But even comments can be misused! OTOH I am able to build things in Go with generics that I would not be very happy building without them.

Yeah I agree. Due to Go's slow moving approach we'll see the biggest impact of generics much later, when they become more prominent in the standard library. A lot of those APIs are necessarily not type safe now and generics would close that gap quite nicely
Post reply on HN