3 ms·

The only Cocoa API that has been deprecated in recent years is drawers. Apple is not going to suddenly rewrite their entire desktop apps and utilities in UIKit/

The only Cocoa API that has been deprecated in recent years is drawers. Apple is not going to suddenly rewrite their entire desktop apps and utilities in UIKit/Marzipan anytime soon (if ever - hell, they won't even rewrite them in Swift anytime soon), so Cocoa is well established and here to stay for a long time. So unless your app is entirely built out of drawers, I don't see how the mere presence of Marzipan can affect your long term business.

swerner 7y ago
QTKit was deprecated, and support for objective-C garbage collection, once praised as the future, was removed altogether.
- vlozko 7y ago
  To the best of my knowledge, there wasn’t much of a difference in programming style going from GC to ARC except for a few exceptions like all those pesky CFMakeCollectable calls that ended up being no-ops anyway.
  - swerner 7y ago
    You have to add all kinds of reference qualifiers (__strong, __weak, ...).
    - plorkyeran 7y ago
      You don't have to explicitly mark things as strong as it's the default. Having to manually break references cycles with weak pointers does make the migration not as simple as just changing the compiler flags, but I've never heard of it being all that difficult. Apple managed to migrate Xcode in a single version.
- kec 7y ago
  Garbage collection was deprecated almost immediately after it was released and has never been supported on iOS (which let’s be honest is the target for 95% of all cocoa developers)
  - xhruso00 7y ago
    Be careful, Cocoa is Mac, UIKit is iOS. Most of iOS developers have minimum Cocoa experience.
    - kec 7y ago
      Cocoa is more fundamental and exists in both (although branded as “CocoaTouch” on iOS originally). The UIKit analog on macOS is AppKit. Also GC/Arc aren’t features of cocoa, but of Objective-C itself.
      - rdsnsca 7y ago
        ARC was added to get ready for Swift.
protomyth 7y ago
Well, to be technical, the OpenPanel API changed pretty drastically too. I would expect that a second round of problem will come up because Swift is going to get access to APIs that Objective-C will not get.
gok 7y ago
This was a developer that didn't even bother moving to Cocoa yet

swerner 7y ago

QTKit was deprecated, and support for objective-C garbage collection, once praised as the future, was removed altogether.

vlozko 7y ago
To the best of my knowledge, there wasn’t much of a difference in programming style going from GC to ARC except for a few exceptions like all those pesky CFMakeCollectable calls that ended up being no-ops anyway.
- swerner 7y ago
  You have to add all kinds of reference qualifiers (__strong, __weak, ...).
  - plorkyeran 7y ago
    You don't have to explicitly mark things as strong as it's the default. Having to manually break references cycles with weak pointers does make the migration not as simple as just changing the compiler flags, but I've never heard of it being all that difficult. Apple managed to migrate Xcode in a single version.
kec 7y ago
Garbage collection was deprecated almost immediately after it was released and has never been supported on iOS (which let’s be honest is the target for 95% of all cocoa developers)
- xhruso00 7y ago
  Be careful, Cocoa is Mac, UIKit is iOS. Most of iOS developers have minimum Cocoa experience.
  - kec 7y ago
    Cocoa is more fundamental and exists in both (although branded as “CocoaTouch” on iOS originally). The UIKit analog on macOS is AppKit. Also GC/Arc aren’t features of cocoa, but of Objective-C itself.
    - rdsnsca 7y ago
      ARC was added to get ready for Swift.

protomyth 7y ago

Well, to be technical, the OpenPanel API changed pretty drastically too. I would expect that a second round of problem will come up because Swift is going to get access to APIs that Objective-C will not get.

gok 7y ago

This was a developer that didn't even bother moving to Cocoa yet