3 ms·
Wow, that looks amazing. It's a really comprehensive guide. > This could have been a paper book but the Rust ecosystem evolves pretty quickly so an online guid
by rekahrv 4y ago
Wow, that looks amazing. It's a really comprehensive guide.
> This could have been a paper book but the Rust ecosystem evolves pretty quickly so an online guide that is constantly updated makes a bit more sense.
:-)
My question:
In which scenarios would you recommend to switch to Rust? When does it provide a clear advantage over Python?
- articsputnik 4y agoWith Rust, you won't have to wait for runtime (in Production) to notice an obvious error like wrong types for example, nor do you have to set up 15 external tools to achieve the same toolchain reliability (pytest, mypy, tox, ...), these things are built-in Cargo (Rust package manager). Of course, Python can be fast enough, and decisions like these are tradeoffs. Still, you'll have to invest a lot of DevOps time in Python to achieve a fraction of the reliability and safety guarantees Rust (and its tooling) provide—a high-level summary of the book's first chapter.