Mac developers see ‘smooth ride’ in transition to Intel-based Macs

“There is one certainty for Mac developers: Change comes often to the Apple world. In the early 1990s, developers had to move their code from the 68000 series of Motorola processors to the PowerPC architecture. In the early aughts, they had to move it again, this time from Mac OS 9 to Mac OS X. And now, just as the dust has finally settled, the cadre in Cupertino has changed horses once again,” Rich Siegel writes for RedNova News.

“It’s been two months since Steve Jobs announced that Apple Computer was going with Intel processors, and in that time, Apple’s transition toolkit has made its way into the hands of the Macintosh cognoscenti. And in that time, it’s become clear that this transition will likely be the easiest of all those yet experienced by Apple developers,” Siegel writes. “Apple has mandated that its developers move their code into Xcode, the company’s native development environment, and for many Apple programmers, this – rather than the move from big endian to little endian – has proved to be the most difficult part of the transition process.”

Full article here.


  1. This sounds like a good opportunity for these software developers to really get their hands dirty, clean up their software, and not simply rely on gratuitous new features. If they have to create a need or demand for upgrades in order to maintain longevity in the business, moving closer to pristine code is well worth the effort to the consumer.

  2. “I don’t think developers should be forced to use Xcode. It may be great, but I still think there should be choice.”

    The only problem is that the other major developing environment (Metrowerks’ Codewarrior) has stopped development. IIRC, they’re going to focus on embedded application development. That’s the main reason companies like Microsoft and Macspeech are now in the process of switching to Xcode.

  3. Devlopers aren’t forced to use Xcode, but the gist here is that CodeWarrior-based projects have to be changed to something else.

    This isn’t Apple’s fault, Codewarrior’s been in a coma for a long time.

    If you do use Xcode, your life if made vastly easier.

    Buy heck 90% of my programming needs are met by perl anyway…

  4. And it’s also that other developers need to embrace transitional processes like Apple has in Xcode. The only way developers will have choice is if they have choice. Of course Apple wants people to use Xcode, but, as a free product, they don’t make anything from it money-wise.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.