3 ms·
Yes, Rust has a very different philosophy to the standard library. As soon as something enters the standard library its API is basically set in stone, since the
by wongarsu 4y ago
Yes, Rust has a very different philosophy to the standard library. As soon as something enters the standard library its API is basically set in stone, since there's no versioning for the standard lib. As a consequence, Rust choses to keep a lot of "must-have" functionality in crates, where it can evolve and compete. (rather than just adding more and more HTTP clients to the standard lib like Python did :) )
- mxben 4y ago> As soon as something enters the standard library its API is basically set in stone Is that really all that different from Python?
- chrismorgan 4y agoNo, that’s the point: if you put this stuff in the standard library, it gets frozen forever, and that’s why Rust doesn’t.
- infinityio 4y agoTo quote the python developers guide: > Because of Python’s conservative nature when it comes to backwards-compatibility, when a module is added to the stdlib its API becomes frozen. So it sounds like they do do something fairly similar, but just a different mindset on adding libraries