Re:The future of my games on Apple and what this means for a...
by spijdar on Monday November 11, 2019 @12:15PM
(#21506569)
It's been longer than that. Core 2 Duos are 64 bit chips, and there were core 2 duo Macs releas e in late 2006, so it's been almost 13 yesrs.
The 32 bit support is actually a bit of a red herring here; the bigger issue for some is Apple dropping support for Carbon, a 32 bit only API made to ease porting of classic MacOS apps from the 80s and 90s to OS X, and itself deprecated in 2012.
I guess Apple could have created a 64 bit version, but it also seems reasonable to expect software developers to have rewritten effected software in that timespan. Carbon was originally a compromise for companies not wanting to learn an entire new OS (NeXTSTEP) and API/libraries when updating their apps for OS X -- the fact some apps still need it today is kind of mind boggling.
Then, I suppose the Win32 API has been stable-ish for far longer.
Re:The future of my games on Apple and what this means for a...
by gowld on Tuesday November 12, 2019 @10:30AM
(#21514824)
What's wrong with Carbon? CLI tools still work 40 year later. Tk/Qt/Swing programs still work 20+ years later. Why not updated and recompile carbon for 64bit?
The 32 bit support is actually a bit of a red herring here; the bigger issue for some is Apple dropping support for Carbon, a 32 bit only API made to ease porting of classic MacOS apps from the 80s and 90s to OS X, and itself deprecated in 2012.
I guess Apple could have created a 64 bit version, but it also seems reasonable to expect software developers to have rewritten effected software in that timespan. Carbon was originally a compromise for companies not wanting to learn an entire new OS (NeXTSTEP) and API/libraries when updating their apps for OS X -- the fact some apps still need it today is kind of mind boggling.
Then, I suppose the Win32 API has been stable-ish for far longer.