3 ms·

There are also a whole bunch of APIs left out of 64-bit macOS, including almost all of Carbon that dealt with UIs (HIToolbox, ATSUI, QuickDraw, Nav Services, Di

There are also a whole bunch of APIs left out of 64-bit macOS, including almost all of Carbon that dealt with UIs (HIToolbox, ATSUI, QuickDraw, Nav Services, Dialog/Menu/Font Manager, etc). None of these APIs have received anything more than bare maintenance in the last 10 years, and evolving the system while keeping them operational has not been easy. In a way, this is the true last step of the Mac OS X transition that started in 2001--the removal of the transitional APIs that made it possible.

Twisell 9y ago
I find it interesting in perspective of the Swift language their are now pushing. Theoretically would’nt programms written in pure Swift today be able to compile for any new hardware plateform, thus avoiding the kind of issues that 32/64 switch faced?
- AstralStorm 9y ago
  Instead you get issues with updating from Swift 1.x to 7.x. The educational story of this sort is the transition between python 2 and 3... not ever done for some packages.
  - spronkey 9y ago
    So much this. When you're a small team, this sort of thing can basically mean having a product vs not.
  - saagarjha 9y ago
    Swift is a new language, so it’s sure to have source breakage in the first few versions. The compiler is now backwards compatible, though.