Hacker News new | past | comments | ask | show | jobs | submit login

It's easy to release often when the releases are small. And smaller releases encourage adoption. You don't want a Python 3 situation where your release is so big your user base refuses to upgrade and you get stuck in a hellhole of perpetual legacy maintenance.



The size of the release is not the issue. The issue is that amount of incompatible changes. They basically dropped the language and made a new one.


That seems fairly hyperbolic, as it's my understanding that some Python 2 modules were able to run on Python 3 with no change, and quite a lot more were able to run with some small set of changes. That doesn't sound like making a new language to me.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: