3 ms·
There's a downside to Python's batteries-included approach though: https://leancrew.com/all-this/2012/04/where-modules-go-to-die/ https://leancrew.com/all-this
by mrec 5y ago
There's a downside to Python's batteries-included approach though:
https://leancrew.com/all-this/2012/04/where-modules-go-to-die/ https://leancrew.com/all-this/2012/04/where-modules-go-to-di...
HN discussion: https://news.ycombinator.com/item?id=3913182 https://news.ycombinator.com/item?id=3913182
The obvious compromise would be to let libraries bake as third-party projects for a good long while until there's a fair amount of consensus that they're the Right Thing To Do, then pull them into the standard library. Java's Joda-Time would be one example.
- smoldesu 5y agoOracle doesn't own Rust though, there's no real push to onboard these features besides the general curb-cutting efforts for newcomers. For the most part, 'integral' crates like serde and tokio have been community-managed without issue so far, so it doesn't make much sense to pull one open-source developers passion project from them and pass it to another.