| ▲ | BigTTYGothGF 2 hours ago |
| I think the python maintainers are still feeling burnt by the consequences of the "batteries included" approach from the old times. |
|
| ▲ | yoyohello13 2 hours ago | parent [-] |
| Most Python developers these days weren't even programming when the 2 -> 3 split happened. Unless you're referencing something else. |
| |
| ▲ | denimnerd42 2 hours ago | parent [-] | | the batteries included approach is the stdlib that can do everything. turns out it’s hard to maintain and make good. | | |
| ▲ | yoyohello13 an hour ago | parent [-] | | Yeah that's true. Go seems to be handling the 'fat stdlib' approach pretty well though. I really don't want Python to got the path of Rust where nothing is included. |
|
|
