3 ms·
I agree completely. None of these examples are going to convince a C++ programmer who's already sunken the cost of learning the language to switch to rust. Som
by CountSessine 12y ago
I agree completely. None of these examples are going to convince a C++ programmer who's already sunken the cost of learning the language to switch to rust.
Something I realized at some point is that these "language A vs language B" comparisons aren't really there to convince adherents of language B to switch to language A. You'll see lots of comparisons on the web of Haskell/Scheme/Lisp/C#/F#/Ocaml etc put up against really poorly written C/C++ code, with "language A" inevitably coming out of the comparison pretty well.
Thinking back to my days at school, a lot of physicists were telling each other that if they wanted their simulations to run in a reasonable amount of time, they had to code them in C. These comparisons are really aimed at them - the message here is, "yes, a really great C programmer could write machine-optimal FFTs or whatever in C, but the code that you, a beginner, will end up writing could actually end up being not much faster and in some cases perhaps even a lot slower than the equivalent code in Haskell/etc".
- im2w1l 12y agoNowadays you would compute the FFT's on a GPU. And it does really matter.