Marshal SHI
2 min readOct 2, 2021

--

Hi. Good question. Here is my personal thoughts.

There is a sentence from rust community:

> Go for the code that has to ship tomorrow, Rust for the code that has to keep running for the next five years.

Python vs Rust gives me same feeling. If we want to have a system which could run asap, then Python. There are a lot of libs and also it's simple to run the code. We don't need worry where the data is saving and how to pass the value.

But when the python system is growing and when it's large enough (if the system need > 1 person), then we have to be careful. We need to define the code style and also whether we should use `typing` or type checker, like `mypy`. More and more rules need to add to make the maintenance simpler.

In Rust, starting is hard. But since the powerful compiler and syntax checker, we could skip "how to define the rules". The code consistency will be from the start of project to the end of it.

It's true. Some Rust libs are developing and need improve. But still, we could find some product ready libs. Like `actix-web`, `tonic` in web. (I saw you are working in DS and AI. I didn't use Rust for both. And in my view, Python is better than Rust currently. But we could see several projects are started in Rust. For instance, a repo at tensorflow github is binding rust for tensorflow).

SO, for me, I will chose Rust over Python if running a long life cycle project.

Thanks

--

--

Marshal SHI
Marshal SHI

Written by Marshal SHI

Robots make our life easier | Robotics, Reinforcement Learning, Web, Python, Rust & Life Hacking. At MotivEdge.io

No responses yet