> Argon agents are working on migrating C/C++ codebases to Rust across Google
Man, I remember back in the days when the cppnext team was refusing to even consider Rust, instead looking at absurd stuff like Carbon and Swift (!), even though half of the engineering staff already knew where this was headed. I hope they got a few good promos out of the delays at least.
Longtime Google engineers have it particularly bad. Some of it could be bad-faith promotion hunting I suppose, but the core problem is that their "find something to work on" culture leads to some insanely dysfunctional ideas around ownership. In the reverse, too; only at Google can you be the head engineer for a service necessary for $10B in ARR and never really realize it.
Also the internal tooling culture there is just insane. I'll never forget the day the last SUPER_ESSENTIAL_TOOL was marked as "Deprecated - do not use!" while the only replacement was still marked "Pre-release -- use at your own risk!". I can't pretend to know what dynamics led to that cause it was so far from my org, but I can't imagine they were healthy ones!
tazjin · · focus · HN ↗
Man, I remember back in the days when the cppnext team was refusing to even consider Rust, instead looking at absurd stuff like Carbon and Swift (!), even though half of the engineering staff already knew where this was headed. I hope they got a few good promos out of the delays at least.
baq · · focus · HN ↗
bbor · · focus · HN ↗
Also the internal tooling culture there is just insane. I'll never forget the day the last SUPER_ESSENTIAL_TOOL was marked as "Deprecated - do not use!" while the only replacement was still marked "Pre-release -- use at your own risk!". I can't pretend to know what dynamics led to that cause it was so far from my org, but I can't imagine they were healthy ones!