4 ms·

Go is probably a better pick in this case.

• throwaway127482 1y ago
  With data intensive Go applications you eventually hit a point where your code has performance bottlenecks that you cannot fix without either requiring insane levels of knowledge on how Go works under the hood, or using CGo and incurring a high cost for each CGo call (last I heard it was something like 90ns), at which point you find yourself regretting you didn't write the program in Rust. If GC in Rust could be made ergonomic enough, I think it could be a better default choice than Go for writing a compiled app with high velocity. You could start off with an ergonomic GC style of Rust, then later drop into manual mode wherever you need performance.
• ViewTrick1002 1y ago
  Inviting in nil errors, data races and a near non-existent type system.
• bryanlarsen 1y ago
  It's possible to turn off GC for most of go and only use it where I want it? That's what this solution gives us for Rust.