No More Codewarrior for Mac OS X

wandazulu writes "According to an announcement posted on the Carbon developer's mailing list, Metrowerks announced at AdHoc that the forthcoming release of CodeWarrior 10 will be the last for Mac OS X. This isn't surprising given that Apple is transitioning to Intel chips and Metrowerks has exited the Intel market, but it's still the end of an era. CodeWarrior literally saved Apple's bacon during the transition to PowerPC in the early 1990s by shipping the first working set of developer tools for the new platform. And since then CodeWarrior has been the main toolkit for commercial development on the Mac (especially pre-Xcode)."

Comments

Do you know what 'literally' means?

[Anonymous Coward]

"CodeWarrior literally saved Apple's bacon during the transition to PowerPC in the early 1990s..."

Then Steve-the-vegan came back and banished the bacon forever!

The end of MacHack

[CokeBear]

The more significant news this weekend is that this was the last MacHack/ADHOC conference. It was one of the best, and will be missed.

FUD!

[andy55]

83% of Mac developers use XCode primarily
74% of commercial Mac developers use XCode primarily.

Source?? This is FUD, and that's the reason the parent poster was AC--ugh!

If you read the xcode apple maillist or develop mac os software for large scale apps, you'd know the figures are actually around the opposite. The truth of the matter is that the latest version of Xcode, 2.1, still has *major* potholes for any medium sized or larger projects. A simple read through the last few weeks of the xcode users apple maillist will reveal this--CodeWarrior users are furious since they're effectively being told that they need to use Xcode (b/c of the intel switch) while Xcode is a far cry from being able to swallow medium (or larger) projects (I myself am in this situation).

Xcode 2.2 promises to stop of the bleeding, but even one of the apple xcode devs said point blank that many of the UI inadequacies won't be addressed until the "next major release" (meaning Xcode 3! -- how far is *that* off?). And then there's GCC 4.0 being broken for certain things. Sure, this has nothing to do with Xcode, but it's more reason CW people like myself are still totally turned off from making the switch.

Anyway, what's more scary is the wacko who posted the parent comment--to just blatantly make up weird shit like that--wtf.

Re:where is metrowerks going to go from here?

[jamus]

Metrowerks is now owned by Freescale, which was spun off from Motorola.

Metrowerks' About Page

Re:Intel decision wasn't a blood oath

[dair]

Has Metrowerks suddenly developed an allergy to generating x86 code? I doubt it.

Pretty much - they sold their x86 tools to Nokia a month or so before WWDC, and that type of transfer typically includes a "you don't get to claw it back later" clause. Which I guess would have been a reasonable thing to agree to at the time, as what are the chances Apple are going to switch to x86...

Re:where is metrowerks going to go from here?

[SmittyTheBold]

Well, MS has XNA, so most developers will be using Visual Studio-derived tools for XB360 development. I don't know about Sony's development system, but it makes sense to assume Nintendo will continue to use CodeWarrior.

Re:Intel decision wasn't a blood oath

[bcombee]

Nokia uses the x86 tools as part of their simulator toolset, letting you build a Symbian application for a Win32 library and debugging it on the desktop before building it for the harder to work with hardware.