3 ms·
Who are you going to blame when applications start breaking because Apple removes or changes the functionality of a private function? [1] without warning? When
by scarface74 7y ago
Who are you going to blame when applications start breaking because Apple removes or changes the functionality of a private function? [1] without warning?
When you are writing any software that has a public API you should feel no obligation to change the functionality or completely remove a private method without warning.
[1] I refuse to call it a private API. An API is public documentation of the inputs and expected behavior of a dependency. It should be a completely black box how that functionality is implemented.
- throwGuardian 7y agoBlame the developer? Which is why, when an app breaks on the Mac store or app store, users pound the app with 1-star reviews. Even if the breakage happened from a platform (iOS or MacOs or Android) bug. This is not Apple "watching out" for the developers, no matter how much you spin it