As @mitsuhiko says in the article, it is very easy to export symbols from a Rust library so that they can be used via CFFI, so the possibility of "dropping down to Rust" instead of "dropping down to C" is very attractive to me.
I also have Julia in my mind for my next scientific computing (image processing, DSP) project.
In comparison, Julia has relatively few web frameworks, GUI toolkits, etc..
https://github.com/micklat/NimBorg
I've been able to call into the Nim side from Python by treating the Nim code as C functions to call. That works, but it would be interesting to come up with a more Pythonic way of doing that.
* harder, but not impossible
To me, at least, Rust provides a compelling alternative to C in the Python+C combination. Coming from Python, writing C is pretty unergonomic; it's super-easy to shoot yourself in the foot and have your program die with an inexplicable segfault, which feels pretty alien for someone used to nice pretty stack traces. Rust promises to make that a lot more pleasant by being memory-safe, while still making good performance promises.
Rust is for performance critical applications where you cant afford garbage collection. You would choose Rust as an alternative to C or C++.
Using Rust will certainly not make your life easier compared to Python. But you could use Rust on some projects where Python is not possible.