Frontpage web editor6/6/2023 Apple did not create a 64-bit version of Carbon while updating their other frameworks in the 2007 time-frame, and eventually deprecated the entire API in OS X 10.8 Mountain Lion, which was released on July 24, 2012. As the market has increasingly moved to the Cocoa-based frameworks, especially after the release of iOS, the need for a porting library was diluted. "Carbon was an important part of Apple's strategy for bringing Mac OS X to market, offering a path for quick porting of existing software applications, as well as a means of shipping applications that would run on either Mac OS X or the classic Mac OS. The difference thought is that PPC on NT never took off so there's something like 4 or 5 Apps for NT versus the thousands or hundreds of thousands for OSX. You can't run the PPC version of an NT app on modern hardware just as you can't run the PPC version of an OSX app on MacOS. It was mostly a recompile unless the App used assembly. > Can you run the PPC version of any Windows NT apps?ĭeveloping for PPC was much like targeting x86 and PPC on a OS X. It took them 12 years to get to the point where they felt comfortable killing it off and almost 20 years before they actually could. Since it's inception, Apple wanted Carbon dead, it required them to rewrite core parts of OpenStep in C and they had to maintain them alongside their Obj-C equivalents. So Apple came up with Carbon, which was sort of a port of Classic APIs to OS X, but because the two operating systems were so different it wasn't anywhere close to a 1:1 copy and required developers to port to it. ![]() Apple wanted a clean break in the form of Cocoa but the community said no. That was met with a resounding "no" from the community.Ĭarbon was never suppose to exist, the Classic APIs were not memory safe, don't support thread, and had a lot of other issues. ![]() PPC to x86 possibly the smoothest transition I've seen in my lifetime, for most it was just a recompile, and I'm convinced it was only as smooth as it was because of the shit show transition to OS X.Īpple announced it's plans to move to OS X in 1997 and that they'd ship an emulator, Blue Box, to run classic apps. I mean, just as an example - I can run Photoshop 6.0 (from 2000) on Windows 10 (certainly no thanks to Adobe), but no chance for PS 7.0 even on Leopard. And while Microsoft did a lot even to prevent and/or work around issues with notorious software (hello Adobe! :) ), Apple was far less willing to do so. Sure, Carbon and Rosetta certainly were no mean feat, and the drastic PPC/x86 break is something Microsoft never really had to deal with (heh, the biggest problem trying to run a PPC/MIPS/Alpha based NT application today is actually finding one :) ).īut Apple never went to the same lengths as Microsoft regarding backwards compatibility, and while Carbon and Rosetta immensely eased the transition, the continuity definitely wasn't comparable and it was never transparent to the developers (and in Apple's defense, this was never their intention and they always were quite open about it.)įor one, Rosetta (and thus PPC compatibility) was dropped with Lion in 2011, so no amount of Carbon would help 10.1 applications after that.Īnd even with Rosetta, each release, especially after Tiger, came with quite a list of API changes and deprecations (with the whole of Carbon declared obsolete in 2012) - and and increasingly longer list of high-profile software that would not run anymore and require an update or upgrade. Sounds to me more like the ported programs were short lived - and IMO, in that they are not entirely wrong. Found some random repo that claims it's a fork of a good one with a bug fix? Build it and run it! I would also suggest that it in the Linux world where running random binaries as root is most common. Mac users buy very, very expensive hardware to do very specific tasks, and "hack around" is often not a good enough justification for the most expensive personal computers money buys. It may be more common in Windows, but I would challenge that since Windows is basically free and runs on anything from a raspberry pi up, the vast majority of "hacky" stuff happens in Windows and Linux. I suppose that's common among kids who don't buy things (but I don't believe those tools run as admin). Maybe you're thinking of software pirates using scene software as keygens or DRM-defeaters. Maybe you're thinking of the hacker culture of the 80s, but gamers today use launchers to manage downloading, installation and setup of software. I have literally never heard of a "gamer" running shady binaries with administrator privilege in my entire life.
4 Comments
Leave a Reply. |