4 ms·
I agree that there's a sound reason for this, but I can't help but think that API versioning would be the more correct way to do it. This is how you pile up unn
by Lorkki 8y ago
I agree that there's a sound reason for this, but I can't help but think that API versioning would be the more correct way to do it. This is how you pile up unnecessary complexity.
- macintux 8y agoI’d agree, except what Apple is doing here is orthogonal to backwards compatibility. They’re fixing buggy apps, some of which are buggy because they rely on undocumented behavior.
- rarepostinlurkr 8y agoIf it worked yesterday and after an OS update it still works how is that not backwards compatibility? Does it matter to a user if the change was due to some “buggy apps”? If it works, it works.
- AceJohnny2 8y ago> but I can't help but think that API versioning would be the more correct way to do it I'm not sure what you mean, because to me that's what they're already doing, where the API version maps to the OS version. When compiling in XCode, you can select which OS version you're targeting, and that essentially gives you which API version you're targeting.