4 ms·
The point of the article is that Go and Rust don't actually serve the same purpose. So asking "Go or Rust" 99% of the time means choose Go. For the other 1% o
by qyv 9y ago
The point of the article is that Go and Rust don't actually serve the same purpose. So asking "Go or Rust" 99% of the time means choose Go. For the other 1% of the time you (should) know that you actually need Rust, not Go.
- lordCarbonFiber 9y agoThe problem with performance is that "you don't need it" right up until the moment you do. It's the same argument startups use for writing their apps in python. You get your "massive dev output" right up until you realize your web app isn't going to scale and you've got to do a full rewrite and runtime errors have burnt out most of your dev team. There's a reason why the lion's share of code written today is Java or C++ and Rust compares much more favorably on the more "enterprisey" merits (stability, expandablility, performance) than the startup merits (how fast can we ship).