I'd agree with that - I haven't developed for Apple, but we run quite a few old applications for Windows at work, and it would be a big problem for us if they stopped working in a new version of Windows.
Removing the old cruft means that old apps stop working; some of those old apps are quite good, and it seems a shame to reinvent the wheel (rewrite new versions of old applications) for each OS release, so I'd definitely favour a balanced approach to removing old APIs (where balanced means trying to assess the amount of applications still in use that are likely to be affected by the change).
Comments
I'd agree with that - I haven't developed for Apple, but we run quite a few old applications for Windows at work, and it would be a big problem for us if they stopped working in a new version of Windows.
Removing the old cruft means that old apps stop working; some of those old apps are quite good, and it seems a shame to reinvent the wheel (rewrite new versions of old applications) for each OS release, so I'd definitely favour a balanced approach to removing old APIs (where balanced means trying to assess the amount of applications still in use that are likely to be affected by the change).