Robin Raymond: Rusty Python - A Case Study

[@filipengstrom3639]

One thing that I have noticed after trying to write rust packages for Python is that there is quite some overhead costs that might be expensive in some cases. It’ becomes apparent when a given solution is done completely in rust. For all the times I’ve tried this it has always ended up with rewriting the whole script in rust. Take my comment with a grain of salt since I’m far from good in pyo3, so I might be doing simple beginner’s mistakes. Anyway cool stuff, hope it finds it way into more real time projects.

[@ttuurrttlle]

It's funny that the 3 "terrible" things about rust that were mentioned are barely even bad. Well, slow compile times aren't as good as fast compile times, but still. The other two are basically pros, the kind of verbosity he mentions is just about static typing which some consider a good thing because it's more explicit. And the "puzzle" bit at worst sounds more like unfamiliarity with rust patterns for lifetimes and at best a positive because puzzles are fun and it guides you into writing better code with its strict compilation rules.

[@julians.2597]

> he kind of verbosity he mentions is just about static typing It's not, take a look at e.g. OCaml, which inspired Rust. Complete type inference with a complex type system is possible and sound. It allows you to only need to anotate what you want.

[@raidensama1511]

IMO learning Rust will make one a better Python programmer. Rust is not difficult provided one has patience and really takes the time to understand borrowing and lifetimes.

[@blanky_nap]

I agree. E.g. learning rust, I finally get better understanding of generics in python. Actually I would continue to learn Rust, but the problem is I am not sure how to use it in my projects on day to day basis.