8 ms·
This is a bit confusing, and, every time I go back to do something with it, it changes. The documentation isn't clear and StackExchange/Medium often don't list
by jollybean 4y ago
This is a bit confusing, and, every time I go back to do something with it, it changes. The documentation isn't clear and StackExchange/Medium often don't list the versions very well.
Old companies often die of bureaucracy - due to their own power and incumbency, they just keep making money, hiring people, doing stuff.
But in this era, the people are 'smart' and now we have the web which allows for infinite churn.
Everything I go to touch has 'changed' - from my own iPhone, Google Play Console etc.., to the packages in my build, in addition, the layers of complexity are so bad much of this requires specialization.
I think we need to start to recognize the cost of churn and complexity because right now we're externalizing it.
When you release V12, you can't just forget that V11 exists. V12 only exists in the context of V12.
For some reason, very smart people have a hard time with this I suggest it maybe organizational.
Python v2->v3 was a bit of a disaster and I would argue, largely avoidable; I'd like to know why they went so wrong ...