3 ms·
As a person who has written Rust code professionally for 4, here's why I returned to python: batteries included. That's it. Having cargo download 1000s of pack
by Zuiii 4y ago
As a person who has written Rust code professionally for 4, here's why I returned to python: batteries included.
That's it. Having cargo download 1000s of package from who knows who for basic functionality is unacceptable. Rust's features, while absolutely phenomenal to work with, just aren't worth having insane npm-style dependency graphs and all the risks they entail. In comparison, Python's built-in modules are a godsend.
So all in all, I think you should continue to stick with python.
- deleted 4y ago[deleted]
- jackosdev 4y agoI still really like Python for scripts and small programs, but I’m always going to use Rust now for CLI’s or anything larger, I get the problem you have with it, but the trade off is worth it for me being able refactor quickly and with confidence as the program grows.
- Zuiii 4y agoFair point. I dearly miss Rust's type system. I think python vs rust is always going to be a tradeoff either way. I just wish we had the best of both worlds in one language. Rust's base language with python's extensive library. Perhaps a new language will emerge that can satisfy both requirement now that Rust has a somewhat stable "safe" FFI. One can only wish.