3 ms·
I don't understand this comment, do YOU actually ship breaking changes to your users and expect them to continue using your code or programs? Just because Apple
by guhidalg 4y ago
I don't understand this comment, do YOU actually ship breaking changes to your users and expect them to continue using your code or programs? Just because Apple does it doesn't mean it's actually a good idea.
- arcticbull 4y agoI, like anyone with a project sporting a major semver number >1 definitely ship breaking changes to my API customers.
- guhidalg 4y agoCan you not? I understand sometimes you absolutely need to change a signature or deprecate a feature, but that should absolutely be the exception and not the norm. Going back to the original post, I find it ridiculous that Apple regularly ships breaking changes (to their APIs) and developers just put up with it. In my minds, it's like being in an abusive relationship where you think if you try a little harder and stay up to date with the latest API version maybe Apple will treat you better (they won't). Apple can get away with it because they own the whole iOS/macOS tower top-to-bottom, but if you want to build trust with your users breaking changes should be the absolute last choice.