3 ms·
It is already three years old. I doubt AppKit, UIKit or any of the predecessors were in a bad state for three whole years after their launch.
by ricardobeat 4y ago
It is already three years old. I doubt AppKit, UIKit or any of the predecessors were in a bad state for three whole years after their launch.
- kitsunesoba 4y agoI can’t speak for AppKit, but UIKit/Cocoa Touch was pretty rough early on. Major chunks of “standard” functionality were missing and standard widgets were somewhat inflexible. It was common to pull in third party libraries and write custom widget code for relatively basic things. Based on my experience, the UIKit dev experience didn’t start to reach the level of completeness it’s known for now until some time between iOS 7 and 9… at least that’s when I remember the number of “required” third party libraries start to steeply decline.
- nemo 4y ago>I doubt AppKit, UIKit or any of the predecessors were in a bad state for three whole years after their launch I was there for Cocoa development in Mac OS X 10.3. AppKit was not mature. I wasn't there but have heard it was less mature in '91 3 years into NextSTEP.
- Longhanks 4y agoAppKit was so not mature that Apple shipped its whole legacy UI framework Carbon for a decade to come, with even the Finder itself taking until 2009 to be rewritten in AppKit.
- pjmlp 4y agoThat was a side effect from the likes of Adobe and Microsoft not wanting to rewrite their Mac OS flagship products into Cocoa than anything else regarding maturity.