4 ms·
I've used some of your code (ripgrep?), and it is fast. I didn't claim it's mysterious, just that every Rust project I see says 'blazingly fast' somewhere on i
by DrBazza 6y ago
I've used some of your code (ripgrep?), and it is fast.
I didn't claim it's mysterious, just that every Rust project I see says 'blazingly fast' somewhere on its web page. Other native languages that are fast (C++, D, etc.) don't seem to feel the need to advertise their speed.
- jedisct1 6y agoRust evangelism task force.
- coldtea 6y agoGolang projects seems to use the same claims too -- even if they're way behind C/C++ etc equivalent projects in performance. In many cases it's just newby devs surprised by how faster (almost for free) they get than some scripting language they used before...
- phkahler 6y agoRust straddles the line between the statically typed, compiled languages and newer more featureful ones that tend to be slower due to things like GC, dynamic typing, running on a VM. For those migrating from C++ they want to advertise it as a better language without performance compromise. For those coming from the other side the primary benefit may actually be the increased performance. In the case of Alacrity the author did go to great lengths to optimize and benchmark the text rendering. It really is fast. That's not usually an issue in a terminal, but I have had rare moments when an excessive amount of text output caused me to wait for the terminal to catch up.
- ubercow13 6y ago>the author did go to great lengths to optimize and benchmark the text rendering I think they went to great lengths to optimise the text output buffering but not necessarily the text rendering. Their benchmarks involving catting large files don't require the rendering to be fast.