4 ms·

I'm a big fan of Rust, but I have to admit its up-front development costs are not always worth the trouble. Rust isn't great for rapid prototyping, where Pytho

I'm a big fan of Rust, but I have to admit its up-front development costs are not always worth the trouble. Rust isn't great for rapid prototyping, where Python excels. Python is quicker for the first few hundred LoC, but I quickly find myself reaching for Rust enums (aka ADTs or sum types), match expressions, and the assurances of static typing. It's also a bit annoying dealing with &str vs String. I frequently find myself writing things like "foo".to_string(). It's also difficult to build Rust with Bazel, and possibly other non-Cargo build systems.

singhrac 4y ago
It isn't fast (really as far as you can get from "zero cost abstractions") but you can have Rusty enums via sum types in Python, and a poor man's match expression. It's not even that bad, really. With Pylance (or possibly mypy, haven't tried) the experience of writing typed Python is quite good.
- RussianCow 4y ago
  > the experience of writing typed Python is quite good. Except for all the third-party libraries that don't have type information, which was most of them last time I checked. (Maybe this has gotten better recently? I admit I haven't used Python much in about two years.)