4 ms·

Rust puts you very close to the metal, which can be great for writing high performance code, while forcing you to be very explicit about how you use memory. Th

Rust puts you very close to the metal, which can be great for writing high performance code, while forcing you to be very explicit about how you use memory. This is great if memory managment and high performance are a big concern for you, if they are not you might want to choose a language like Go or Node which allow you to gloss over such details until they really become an issue. Do not fix problems you do not have by throwing Rust at them, but feel free make the climb of learning it to expand you horizon. :)

vvanders 8y ago
I'll throw out one more, which is that Rust does a great job at running on a diverse set of platforms(this is distinct from architectures). If you wanted to run one codebase across Desktop(Win32, OSX, Linux), Mobile(Android, iOS) and Web(Asm.js/WASM) you'd usually have to resort to a scripting(perf-impact) or C/C++(compiler differences, poor dependency management). With Rust I can do all that one from one Cargo.toml and a codebase that just works for all my platforms(modulo any forking inside libs that use "target(win32)", etc). For someone who's done that most of their career it was amazing to see how solid and straightforward that is with Rust.
Yoric 8y ago
In my experience, this is true not just of memory management, but also of all sorts of safety guarantees. I currently write a (de)compression library in Rust, and the type system is very helpful for all sorts of things beyond memory management. I would not write that specific code in Node.
deadcoder0904 8y ago
> Do not fix problems you do not have by throwing Rust at them Thank you. I write mostly Node & wanted to try Go for a long time because of performance & then I heard that Rust is even faster. So I thought I would learn that. But you are right, I don't have any problem with Node. Its working great for me. :)

vvanders 8y ago

I'll throw out one more, which is that Rust does a great job at running on a diverse set of platforms(this is distinct from architectures). If you wanted to run one codebase across Desktop(Win32, OSX, Linux), Mobile(Android, iOS) and Web(Asm.js/WASM) you'd usually have to resort to a scripting(perf-impact) or C/C++(compiler differences, poor dependency management). With Rust I can do all that one from one Cargo.toml and a codebase that just works for all my platforms(modulo any forking inside libs that use "target(win32)", etc). For someone who's done that most of their career it was amazing to see how solid and straightforward that is with Rust.

Yoric 8y ago

In my experience, this is true not just of memory management, but also of all sorts of safety guarantees. I currently write a (de)compression library in Rust, and the type system is very helpful for all sorts of things beyond memory management. I would not write that specific code in Node.

deadcoder0904 8y ago

> Do not fix problems you do not have by throwing Rust at them Thank you. I write mostly Node & wanted to try Go for a long time because of performance & then I heard that Rust is even faster. So I thought I would learn that. But you are right, I don't have any problem with Node. Its working great for me. :)