4 ms·
For an overwhelming majority of applications out there, it really was just "recompile and it works" or even using Rosetta for the interim, until the developer g
by Zev 16y ago
For an overwhelming majority of applications out there, it really was just "recompile and it works" or even using Rosetta for the interim, until the developer got around to it. Apple even created a script that automatically converted scalar types into an architecture-safe equivalent (int -> NSInteger, for example).
Final Cut, Adobe CS and a few other major products are the exception to the migration, not the rule. I've spoken to people who used to work on Final Cut. It has one of the largest codebases that I've ever heard of. Plus, Final Cut wasn't done in Objective-C and Cocoa. It is a C++ application with a completely custom UI, done by Macromedia over a decade ago. Its not even a full 64-bit application yet.
- deleted 16y ago[deleted]
- sudont 16y agoThe problem with that is Apple is a consumer-facing company, and one that targets a subset of early-adopters in VALS known as "experiencers." This specific psychographic is well known for spending money on products with social cache. This social value is partially driven through the "wow" factor of Apple's secretive product release cycle, meaning that developers who don't like it can go lump it and head over to developing for Microsoft or Google's platforms. When you say they sacrifice "users," you're right, but those users aren't priority #1. EDIT: Parent comment was deleted. Was about how inconsistent product release cycles and roadmaps degrade user experience.