2 ms·

I’m curious what he means by Google changing and the Go project changing

by r0nan 2y ago

LVB 2y ago
re: Go, I did wonder if there was any connection to Russ leaving (https://news.ycombinator.com/item?id=41132669 https://news.ycombinator.com/item?id=41132669)
- nikolayasdf123 2y ago
  yes, looks like related
- atombender 2y ago
  Russ Cox has not left. He's still on the Go team at Google, but he's stepped down from his position as tech lead.
  - rsc 2y ago
    Officially, I have left the Go team too; I started on a new team at Google a few weeks ago. I still use Go quite a bit, I still talk to people on the Go team regularly, and you will still see the occasional code change, code review, or blog post from me. Most importantly, I have high confidence that the team we built will do an excellent job continuing the work.
    - atombender 2y ago
      Gotcha. In your golang-dev announcement you wrote that you are "not leaving the Go project", but maybe there was another announcement?
      - rsc 2y ago
        The parent comment is the first time I've said anything publicly (it has only been a few weeks). I didn't feel like it needed an announcement, but since it came up, it seemed worth correcting. It's not a state secret. :-) In my August announcement, I was careful to say I wasn't leaving the Go project. I'm still involved with the Go project and expect to keep being involved. I'm just not officially on the Go team at Google anymore. Stepping back from the actual team to give others room to lead always seemed to me both likely and appropriate.
    - kragen 1y ago
      That's interesting! I hope you're excited about the new team!
    - philosopher1234 1y ago
      Very curious what you’re working on now, if you’re willing to share
- DannyBee 2y ago
  Russ didn't leave. But this is also different, AFAIK. In this case I expect it's more related to how the engineering ladder has changed at Google over time, and the effects of cost cutting placing pressure to conform to the ladder, even when the ladder doesn't reward what it necessarily should be rewarding. That's about as unobtuse as i can be about it, for various reasons.

I’m curious what he means by Google changing and the Go project changing

by r0nan 2y ago

I’m curious what he means by Google changing and the Go project changing

LVB 2y ago

re: Go, I did wonder if there was any connection to Russ leaving (https://news.ycombinator.com/item?id=41132669 https://news.ycombinator.com/item?id=41132669)

nikolayasdf123 2y ago
yes, looks like related
atombender 2y ago
Russ Cox has not left. He's still on the Go team at Google, but he's stepped down from his position as tech lead.
- rsc 2y ago
  Officially, I have left the Go team too; I started on a new team at Google a few weeks ago. I still use Go quite a bit, I still talk to people on the Go team regularly, and you will still see the occasional code change, code review, or blog post from me. Most importantly, I have high confidence that the team we built will do an excellent job continuing the work.
  - atombender 2y ago
    Gotcha. In your golang-dev announcement you wrote that you are "not leaving the Go project", but maybe there was another announcement?
    - rsc 2y ago
      The parent comment is the first time I've said anything publicly (it has only been a few weeks). I didn't feel like it needed an announcement, but since it came up, it seemed worth correcting. It's not a state secret. :-) In my August announcement, I was careful to say I wasn't leaving the Go project. I'm still involved with the Go project and expect to keep being involved. I'm just not officially on the Go team at Google anymore. Stepping back from the actual team to give others room to lead always seemed to me both likely and appropriate.
  - kragen 1y ago
    That's interesting! I hope you're excited about the new team!
  - philosopher1234 1y ago
    Very curious what you’re working on now, if you’re willing to share
DannyBee 2y ago
Russ didn't leave. But this is also different, AFAIK. In this case I expect it's more related to how the engineering ladder has changed at Google over time, and the effects of cost cutting placing pressure to conform to the ladder, even when the ladder doesn't reward what it necessarily should be rewarding. That's about as unobtuse as i can be about it, for various reasons.