In a longer live context(more data crunching) Rust will win by even a greater margin, as performance improvements will compound. I know from benchmarking various Rust vs Go vs Node.js scenarios, and as the volume of…
'After spending some weeks playing with Rust,'... he is new to Rust and keeps using String, accepting `&String` as args etc this is not tuning. This would be caught by linters like clippy telling you to double check it.…
Rust, no surprises here.
Perfectly valid to include it because that is what you will experience when using it.
He figures that out in his 2nd article, where he now finds Rust is 1/8th of the time of Node.js.
In a longer live context(more data crunching) Rust will win by even a greater margin, as performance improvements will compound. I know from benchmarking various Rust vs Go vs Node.js scenarios, and as the volume of…
'After spending some weeks playing with Rust,'... he is new to Rust and keeps using String, accepting `&String` as args etc this is not tuning. This would be caught by linters like clippy telling you to double check it.…
Rust, no surprises here.
Perfectly valid to include it because that is what you will experience when using it.
He figures that out in his 2nd article, where he now finds Rust is 1/8th of the time of Node.js.