5 ms·
> I think the two big problems with the Python 3 rollout When Python 3 was announced I thought "this is a great way to rollout". After a few years I thought "w
by reggieband 8y ago
> I think the two big problems with the Python 3 rollout
When Python 3 was announced I thought "this is a great way to rollout". After a few years I thought "what a terrible rollout, even I haven't changed to version 3 100% yet because of some libraries I rely on are still only verion 2". Now I'm back on the positive side of things. It turns out, in the grand scheme of things, 5+ years for a new version to be adopted didn't really affect me in a negative way. I'm back on the "slow and steady wins the race" bandwagon.
- nordsieck 8y agoThere's a bit of survivorship bias there. There was a very real chance that Python would get replaced by another language in the same way that Ruby and Python replaced Perl. If that had happened, you'd probably still be in the "what a horrible rollout" frame of mind.
- vgy7ujm 8y agoNone of those really replaced Perl...
- antod 8y agoI seem to remember that Ruby was already replacing Python pretty heavily 10 years ago. Rails was gaining momentum at a huge rate and Python web frameworks were dying, tools like Puppet were on the rise etc. The full history of Perl 6 still lay ahead too. If it hadn't have worked out in the end, it would be just as relevant to claim "what a horrible rollout" was just the benefit of hindsight talking. I think the Python devs and community need to take some credit for managing to pull off that transition successfully (even if it took longer than most expected). And to claw their way back into relevance again. And every other language community now has a case study they reference during discussions about language upgrades :)