3 ms·
>"In this post, we will look at a common source of bad performance on Rust code that can trip up even veteran developers, and what you can do when this happens
by FpUser 5y ago
>"In this post, we will look at a common source of bad performance on Rust code that can trip up even veteran developers, and what you can do when this happens in your programs."
"Veteran developers", the sort of who would use Rust after having worked in C/C++/etc would know very well that buffering on very granular IO is a must except some specific situations. Otherwise they're anything but. And it has nothing to do with Rust. This is of course when IO libraries used do not already take care of that.
- DangitBobby 5y agoThe defensive tone by people in this comment section worried that this is some attack on rust is surprising. Experienced people write bad code sometimes. Rust standard library may or may not encourage people to write poorly performing code sometimes if they aren't paying attention to (or don't know) fundamentals. Chill.
- FpUser 5y agoI am not using Rust as I have nothing to gain from it ROI wise. So there is nothing for me to defend. And I am totally cool, no need to chill.