3 ms·

> This complaint says far more about the developer than Apple. Yes, it says that they didn't bother to waste resources doing unnecessary changes. But it also

> This complaint says far more about the developer than Apple. Yes, it says that they didn't bother to waste resources doing unnecessary changes. But it also says about Apple that they do not respect the time and resources of the developers that bother to support their platform. There is no way to spin Apple breaking APIs and programs that people have worked on (for developers) and bought (for customers) in a positive way.

eitland 7y ago
> Yes, it says that they didn't bother to waste resources doing unnecessary changes. Keeping up with API changes from a decade ago doesn't qualify as unnecessary. > There is no way to spin Apple breaking APIs and programs that people have worked on (for developers) Here's the point. Apple isn't doing that. Apple don't visit customers with old macs to push breaking patches. What happened is the developers made something that worked on old macs, didn't put in the effort to keep it up to date and are now complaining that Apple won't put in the efforts to support the old APIs on new systems anymore. > and bought (for customers) in a positive way. This is the developers fault I guess.
- badsectoracula 7y ago
  > Keeping up with API changes from a decade ago doesn't qualify as unnecessary. The API didn't change, it worked until Apple decided to break it in a subsequent version of macOS. > Here's the point. Apple isn't doing that. Apple don't visit customers with old macs to push breaking patches. They broke the API in new macOS. > What happened is the developers made something that worked on old macs, didn't put in the effort to keep it up to date and are now complaining that Apple won't put in the efforts to support the old APIs on new systems anymore. Yes, that is exactly the issue: Apple shouldn't have broken the API in the new macOS. The developers are perfectly in their right to complain about Apple breaking their applications and forcing them to waste time rewriting code that already worked to do the exact same thing only now in a different way because Apple doesn't care about the developers' time. And yes, it is all on Apple - the breakage wasn't forced on Apple, it was something Apple decided to do.
  - Klonoar 7y ago
    It’s been deprecated with warnings for years, this isn’t the same as “breaking”.
    - badsectoracula 7y ago
      If in OS version N a program works and in version N+1 the program doesn't work, then the OS version N+1 broke the program. That is all there is to it, anything else is just excuses.`

eitland 7y ago

> Yes, it says that they didn't bother to waste resources doing unnecessary changes. Keeping up with API changes from a decade ago doesn't qualify as unnecessary. > There is no way to spin Apple breaking APIs and programs that people have worked on (for developers) Here's the point. Apple isn't doing that. Apple don't visit customers with old macs to push breaking patches. What happened is the developers made something that worked on old macs, didn't put in the effort to keep it up to date and are now complaining that Apple won't put in the efforts to support the old APIs on new systems anymore. > and bought (for customers) in a positive way. This is the developers fault I guess.

badsectoracula 7y ago
> Keeping up with API changes from a decade ago doesn't qualify as unnecessary. The API didn't change, it worked until Apple decided to break it in a subsequent version of macOS. > Here's the point. Apple isn't doing that. Apple don't visit customers with old macs to push breaking patches. They broke the API in new macOS. > What happened is the developers made something that worked on old macs, didn't put in the effort to keep it up to date and are now complaining that Apple won't put in the efforts to support the old APIs on new systems anymore. Yes, that is exactly the issue: Apple shouldn't have broken the API in the new macOS. The developers are perfectly in their right to complain about Apple breaking their applications and forcing them to waste time rewriting code that already worked to do the exact same thing only now in a different way because Apple doesn't care about the developers' time. And yes, it is all on Apple - the breakage wasn't forced on Apple, it was something Apple decided to do.
- Klonoar 7y ago
  It’s been deprecated with warnings for years, this isn’t the same as “breaking”.
  - badsectoracula 7y ago
    If in OS version N a program works and in version N+1 the program doesn't work, then the OS version N+1 broke the program. That is all there is to it, anything else is just excuses.`