|
|
|
|
|
by KajMagnus
26 days ago
|
|
Aren't you overlooking the main point of the article?, the reason they migrated: > concurrency — eliminating data races essentially, which we had before. Really gnarly bugs > this is the one teams report most enthusiastically. The classes of bugs that survive go test -race and reach production (data races, nil dereferences, missed error paths) just don’t compile in Rust. Oncall rotations are typically very boring after a Rust migration. ... > I hadn’t had to chase down a crash, or some weird multi-threaded race condition, or some of these other things which actually consumed a huge amount of my time before. (They say at InfluxDb) That's not a Rust vs. Go slapfight? Instead, sounds like a good judgement to me |
|