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

The author doesn't seem to understand the idea behind this, which I very much agree with, that a new major version should be handled as a new module. You are breaking contract with your existing users, upgrading will have difficulties for them.

Ross Cox explains the concept in this talk from 9:20: https://youtu.be/F8nrpe0XWRg?t=560






You are breaking contract with _some of_ your existing users, upgrading will have difficulties for _some of_ them.

I regularly update across major versions of packages in other languages and don't touch a thing other than the package version. I appreciate the version bump so I can do my due diligence to research the changes, but I just don't use the entire API of libraries in most cases so I'm not always affected by changes.




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

Search: