3 ms·
I disagree with your premise that production systems require API stability in all thirdparty dependencies.
by wesm 9y ago
I disagree with your premise that production systems require API stability in all thirdparty dependencies.
- dogruck 9y agoI also disagree. I would agree with "won't use because the prod release has a lot of bugs." But APIs change.
- dotancohen 9y agoStability does not imply immutability, but rather established. In new projects it is common for a method or class to change direction or role as it develops, which may bring with it a refactor of identifier names, parameters, and such. After the class has been used for some time in different contexts these changes happen less and less, hence we call the class stable. A 1.0 release implies this stability. Third party dependencies are still free to mutate their APIs, but when maintaining a production system you don't want to be mole-whacking API changes every point release.