3 ms·

I agree with you, developers do get excited when are using newer technologies but the question is what if a new problem arises and they might not be able to fin

• aaomidi 6y ago
  Then they'll have to cross that bridge when they come to it. Nothing of this article gave me the impression that the second they saw this bug they're like WELL TIME TO SWITCH. I'm sure we're glossing over probably hundreds of hours of investigations by dozens of people.
  • jhgg 6y ago
    We kept dealing with GC pauses in go, and eventually after investing a bunch of time trying to fix this - we decided to research what it'd be like to rewrite it in another language. The service itself is pretty simple, so it wasn't a gargantuan task. So it was either, rewrite this again in Go (using off-heap data structures to avoid GC pauses, which makes the software both harder to maintain, and also less idiomatic) or try a new language where we won't have these issues - where we don't have to resort to clever hacks to work around the runtime system. Since then we've continued our investment in Rust, after success of this project (and many others we've yet to blog about as well.)