Rust is nice to read because you can see from a function signature what it mutates
If you write slow rust, it's very easy to read, and still plenty fast.
Rust is nice to read because you can see from a function signature what it mutates
If you write slow rust, it's very easy to read, and still plenty fast.
For a server using a DB, all of your methods are calling out to data stores.
People talk about mutability a lot but the vast majority of Python code I see in the wild is SSA and has _very_ little mutability to begin with.
Of course ownership still has its costs. Lots of "I guess I'm copying this dict because I don't know if the owner will modify it or not" issues.
I think people overestimate how much they'll get from `&mut` annotations on business logic, and undersestimate how much line noise they'd get from a lot of the other stuff that happens in a lot of business logic.
Granted, I'm coming from a web-dev/Django perspective, where duck typing and overriding methods in subclasses is used heavily. And a lot of that doesn't have a nice 1:1 equivalent in the Rust model.
(I enjoy Rust BTW, just don't feel particular excitement about shuffling around strings in it)