Submitted by 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 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).
CodeWarrior to Cease Development on OS X
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
I would say it’s sad for them. Clearly the Apple becoming a “switcher” put a dent in any plans they could have had. Of course I don’t think anyone is stopping them from making a intel version, which their current customers might like if it means they can click a button and make a few changes and be good to go like some developers will be able to who use X code.
At the same time, I think anyone not using Xcode for OSX was a fool at this point. It’s there, it’s free, and you know if you use it you will be supported through anything apple does. Not really an issue of which you like more, but using the tools provided by the OS maker definitely makes for a path of least resistance and reduces chances of being in the same boat as CodeWarrior users today.
I think anyone should have taken apple offering X code for free and pushing it so much as a hint. Apple knows if everyone is on board with Xcode they won’t have to worry about loosing people as they move forward with sometimes surprising movements.
Would you blame Metrowerks for dumping Mac OS X after what happened at WWDC? For those who haven’t watched it: Steve Jobs did his best to humiliate developers who used CodeWarrior. Would you blame them after Apple tried getting developers to drop CodeWarrior for some time, according to Jobs during the WWDC keynote? I wouldn’t want to develop for Macs either, given how savagely they attack their life-blood: developers.
As for this “not using Xcode implies you’re a fool” bit, well, a lot of companies have been developing for the Macintosh for years and may have considered the investment in switching to Xcode to be too high. Alternatively, they may have prefered the CodeWarrior environment. Believe it or not, there is not one true path for developer tools. Unfortunately, Apple has tried to make it such. Ultimately, this will probably be to their detriment. (How many applications with a marginal market and which were coded in CodeWarrior will never make the transition?)
Would you blame Metrowerks for dumping Mac OS X after what happened at WWDC?
I think the cause and effect is backwards here. Motorola’s purchase of Metroworks effectively killed their (much despised…) Intel compiler. One major reason for Xcode development was to allow Apple to move beyond Motorola chips (like to the G5 with IBM) without having their nuts in a wrench by Motorola. Even if Apple asked Motorola to make an Intel version of CW, they almost certainly would have said no.
Believe it or not, there is not one true path for developer tools. Unfortunately, Apple has tried to make it such.
Of course there isn’t one true path, but Apple hasn’t gone out of their way to force people to use Xcode. They ship the dev tools with the standard GNU autotools and Make, so people familiar with those can use them. A lot of Mac apps are written in RealBasic. Xcode itself allows you to use external editors (BBedit, etc).
How many applications with a marginal market and which were coded in CodeWarrior will never make the transition?
Probably less than you’d think. Xcode 2 really does have an extensive amount of CW import capabilities. If the app is old enough that an Xcode migration is out of the question, it’s probably a good Rosetta candidate.
Oh give me a break. I was there. Steve Jobs did not GO OUT OF HIS WAY to humiliate Codewarrior developers. He merely said, look, if you’re not using Xcode, you should. And why did he say this so frankly? 1) Xcode is the best development environment for OS X. 2) Xcode is the only development environment well-suited for Intel work in the future. 3) I’m SURE Steve Jobs knew Metrowerks would be moving out of the way once the Intel announcement came out. Metrowerks and Apple work closely together. Don’t tell me Steve didn’t see this coming.
Steve Jobs was not disrepectful in any way – he was merely telling developers what to plan for.
With the arrival of XCode, there’s probably not going to be much demand for other OS X IDEs now. Still, I have fond memories of CodeWarrior, and I can’t help but feel a bit sad to see it die.
> With the arrival of XCode, there’s probably not
> going to be much demand for other OS X IDEs now.
Ah, interesting. Are you sure? Why do you think that? What will Adobe do?
Adobe uses MetroWerks CodeWarrior. If you don’t believe me, look here at the top of page 10:
http://partners.adobe.com/public/developer/en/acrobat/sdk/ReaderOve…
Or look here in order to find out that you need CodeWarrior to build Adobe’s OpenSource libraries:
http://opensource.adobe.com/asl_readme.html
It is not true that “everyone uses XCode”, just like it’s not true that “everyone owns an iPod” or “everyone uses Safari”.
The discontinuation of MetroWerks CodeWarrior is a sad day for Mac developers. Maybe not the worst imaginable thing, that was the Intel switch, but still a sad one.
> With the arrival of XCode, there’s probably not
> going to be much demand for other OS X IDEs now.
Ah, interesting. Are you sure? Why do you think that? What will Adobe do?
Adobe uses MetroWerks CodeWarrior.
Photoshop plugins (the only SDK I’ve used recently) uses CFM binaries, which XCode can’t create.
It will be interesting to see what happens with things like Photoshop: it may be true that XCode/Cocoa apps can simply be recompiled for Intel, but very, very few large commercial programs use either. “Modern” Mach-O is a seriously inferior system in pretty much every respect except being first-classed by Apple and supporting Cocoa. Converting a program the size of Photoshop to Mach-O, not to mention getting it to build on XCode, is a long, complicated job that no one saw much need for until the x86 death march was announced. There was always the hope Apple would relent/change direction again (admittedly unlikely, as Cocoa is pretty tied to Mach-O.)
I continue to predict that a LOT of major apps will be running in Rosetta for a long time to come. Those that aren’t are the ones important enough to Apple for them to provide direct engineering support beyond a few emails.
very people who made them successful. They screw their customers and they screw their partners. The only reason people stay is the battered-wife syndrome.
so, a company needs to not move forward to keep code warrior happy? are you nuts?
The synopsis fails to mention that they DID open source Powerplant (the main reason people might not want to switch from CW to XCode. There’s no word yet on the license. Check out this guy’s blog for more details from someone at Adhoc/Machack.
http://www.drissman.com/blog/archives/2005/07/29/the_codewarrior_ro…
“As for this “not using Xcode implies you’re a fool” bit, well, a lot of companies have been developing for the Macintosh for years and may have considered the investment in switching to Xcode to be too high.”
Yeah, ’cause if we know something is that XCode is expensive!
Please stop taking things out of context, Metrowerks made it clear they were no longer interested in making CodeWarrior a desktop development environment. They were focused on the embedded market, Jobs made it clear that the developers have XCode. It is not going to go away, CodeWarrior is. So whoever is not making the transition, is indeed a fool. Metrowerks was bought by Freescale, and they are interested in making motorola development tools. They droped a lot of the other platforms too, not because Apple forced them to.
Nobody is stopping anyone in making any IDE for OSX. Apple ships one for free, you can take it or leave it. But Metrowerks were not “forced” out of the OSX development market, they just were not interested.
> Yeah, ’cause if we know something is that XCode is expensive!
yeah, and developers work for free when they are porting software right?
“As for this “not using Xcode implies you’re a fool” bit, well, a lot of companies have been developing for the Macintosh for years and may have considered the investment in switching to Xcode to be too high.”
Yeah, ’cause if we know something is that XCode is expensive! … So whoever is not making the transition, is indeed a fool.
XCode is not able to target certain kinds of code for up to twenty million actively used Macs that should not (or do not) run OS X. Therefore, it should come as no surprise to you that there are indeed many developers still building their software in MPW and CodeWarrior, targeting Mac OS 8, 9 and OS X. A migration to XCode for these developers means eliminating Mac OS 8 and 9 support, or maintaining two build systems (one in XCode and one in MPW/Codewarrior). Until Apple’s announcemnt that the only path to Intel-Macs was through XCode, there was no financial incentive for these developers to kill their Mac OS 8 and 9 codebase and migrate to XCode. “Fool.”
Metrowerks also sold off it’s Windows offerings. They are getting out of the desktop market. I doubt it has anything to do with Apple’s XCode tools. XCode has been around for years under various guises – since the earliest versions of Mac OS X. Metrowerks could make a better tool if they wanted to it really wouldn’t be terribly difficult. Note IBM brought it’s high end compiler to Mac OS and stands to make money. LOL yeah Apple forced them to do this, right.
<quote>
a lot of companies have been developing for the Macintosh for years and may have considered the investment in switching to Xcode to be too high.”
Yeah, ’cause if we know something is that XCode is expensive!
<quote>
Using PowerPlant was one of values of CW.
You have to convet tour code to Cocoa.
It cost time… lots of time… and effort, not just the “cost” of free tools.
> You have to convet tour code to Cocoa.
Um, you can also develop C++ Carbon apps with XCode.
I’m not a Mac OS developer (yet?), but I had to use CodeWarrior for BeOS and PalmOS. I say good riddance! That IDE was a big P.O.S. IMO.
Don´t know if Apple is to be blamed here, because seems like Metrowerks apparently lost interest in the desktop market but Apple has this weird habit of alienate developers from its platform. Either by including too much competing aplications into their bundle (therefore leaving little to no incentive to a customer too look out for something else) or by buying whoever is the best at something and promote its version aggressively against everybody else´s product (See the Premiere-Final Cut thing, even if Final Cut indeed might be a better product).
Microsoft is risking to do that as well with its Acryllic, which is incredibly competitive compared to Photoshop (Adobe´s flagship product, mind you!) and some other new technologies that they have been cooking up lately. You don´t make your friends happy when you piss at their backyard, I tell you.
Given the size of Apple´s market share and installed base, one would think that they should work towards improving relationship with developers to attract more of them to the platform, thus bringing more customers to the party as well. But often they seems to do exactly the opposite.
Maybe giving XCode away and shifting to Intel is a good sign that they are changing their behavior, improving their development ecosystem, but only time will tell, I guess.
I don’t really think Apple has been treating third party developers poorly. They gave me a better platform and better tools to work with in Mac OS X than they ever did before.
Everybody said they ripped off Watson. Hello – by name Watson was a rip off of Sherlock. Dashboard was fair game too, Apple was able to provide a better product than Konfabulator.
Premier stopped being developed for the Mac platform by Adobe, this is why it was always slow in benchmark tests and also why Finalcut was developed – you have it a bit back to front
Premier stopped being developed for the Mac platform by Adobe, this is why it was always slow in benchmark tests and also why Finalcut was developed – you have it a bit back to front
No. You got it backwards, not me. Apple did buy a video editing engine called Key Grip from Macromedia that later became the product known as Final Cut Pro.
Not only that, but they did also acquired Nothing Real for its highly acclaimed Tremor and Shake compositing systems at the same time.
Quoting the article available at http://www.digitalanimators.com/articles/viewarticle.jsp?id=7855 :
Rumors abounded that the powers that be at Adobe Systems became pretty tweaked when Apple shipped Final Cut Pro , which some feel is a competitor to Adobe Premiere . Those same Adobe execs have got to be miffed that Apple acquired Nothing Real, which falls into the same category as Adobe After Effects . In spite of pricing that no longer exists, what it all comes down to is Tremor and Shake and After Effects are compositing tools. Granted, After Effects only runs on Mac and Windows platforms, but the fact is, Apple now has a high end 3D compositing solution that the company says it will incorporate into “future versions of its products.”
So what is Jobs and Co. doing, acquiring all these creative media tools? Are they slowly but surely putting together an entire cadre of tools for content creation that will run only on Mac OS X ? What is next? A 3D animation tool along the lines of LightWave 3D or Alias|Wavefront’s Maya? An image editing tool along the lines of Adobe Photoshop ?
What Apple is doing, acquiring these software developers can be described as insanely great or just plain insane.
Actually, I suggest reading the whole article which is quite outdated but describes quite well what these acquisitions meant back at the time.
OS X gave Apple the foundation it needed to build new generations of machines. But to get most of its 25 million or so Mac customers to upgrade, Jobs needed sexy applications. As part of his deal with Gates, Microsoft had agreed to adapt Office and Explorer for OS X. Jobs had assumed that this vote of confidence would inspire third-party developers to come up with software for, say, editing home videos on a computer or managing photos or digital music. But a 1998 meeting in which Jobs asked Adobe Systems executives to develop a Mac version of their consumer video-editing program changed his mind. “They said flat-out no,” Jobs recalls. “We were shocked, because they had been a big supporter in the early days of the Mac. But we said, ‘Okay, if nobody wants to help us, we’re just going to have to do this ourselves.’ “
From the Feb 21, 2005 Issue of Fortune, article by Brent Schendler
This doesn’t come as a surprise, given the lack of enthousiasm Metrowerks has shown for the Mac desktop over the last years.
However, it’s still a sad loss: Less choices than before. There are quite a few points where I think CodeWarrior is significantly better than Xcode, but Apple’s recent moves force me to Xcode. I would love to have the option to use a different IDE than Xcode, but as it stands, there is none (before anyone suggests Emacs and makefiles, please make sure you understand what an IDE is). Anyone interested in writing a Mac dev plugin for Eclipse? I have successfully built Cocoa command line apps with it, but right now it’s a hassle and it doensn’t support application bundles.
Not surprising… Apple is well known for not caring for their developers.
I’ve been one of the chief “reactionaries” the last few years; I was one of the original people talking about the Emperor’s New Clothes through 10.2 or so. I’ve made a fair number of transitions (I switched to CodeWarrior (and C++), after all.) The difference is that all my transitions before IMPROVED my life.
MW is obviously free to do what they need to do to run their business; I can’t blame them for exiting a market where they’re faced with the kind of hostility Apple is showing them. When CW came out Apple didn’t actively kill MPW, they just let it go, and the alternative was much better anyway. With XCode they’re adopting the same “our way or the highway” scorched earth policy they originally did with OSX.
CW was (and still is, allowing for the stoppage of development) the best IDE I’ve ever used, far transcending anything on Windows (C++Builder’s great RAD doesn’t make up for its horrid environment; Visual Studio was apparently designed, like QWERTY, to be as slow and painful as possible.) XCode is a product that I would have tried and then ignored (I have several times, not 2.0 as yet); it simply is not professional quality, in performance, features, or stability, and while I think it’s a neat free toy to include with the OS (a wonderful idea of Apple’s, BTW) it doesn’t meet my needs and I resent having to spend extra time wrestling with it. Of course, now they’ve added a new “feature” (x86 codegen) that helps matters.
It is a frequent mischaracterization of QWERTY that it was designed intentionally to be inefficient. It was designed to avoid crossing the bars used to strike type when used rapidly. It was designed to improve typing speed while avoiding mechanical jamming. If all he had really desired was to avoid jams by reducing the efficacy of typists, employers could have simply hired typists that did not type as well. Or, and I’m sure this will shock you, instruct people not to type as rapidly.
I’ve been a user of both CodeWarrior (version 9) and Xcode, and CodeWarrior definitely has/had advantages over Xcode.
Sure, Xcode is free, but it’s also bloated, slow and buggy. CodeWarrior is simpler, MUCH faster – in both compiler time (though that can be blamed on gcc), and interface snappyness – this is Apple’s fault in Xcode. It also does some things _much_ better than Xcode, such as being able to disassemble the code and see relative hex addresses next to lines of code, for example – which makes going from hex addressed in crashlogs to the code that made the crash so much easier (as opposed to Apple’s recommended way is to use a bunch of complicated command line tools straight from their Technical Note).
Another example is that project files from Xcode are not compatible with each other, and that Xcode versions are tied to the OS versions – that is, you can’t run Xcode 2 (tiger’s) on Panther, and same for Xcode 1.0 on Jaguar (where the dev tool was called Project Builder). This makes it hell for Open Source projects, which can’t guarantee that all developers run the same OS. In one such project, we have like 4 versions of the project files, each for a different version of Apple’s dev tools, to make sure all the developers can contribute. When a file is added to the project, every project file has to be updated with the change, its a major pain in the ass. Something like CodeWarrior 9, however, supports Mac OS X 10.1 to 10.4, making a single project file be able to be used regardless of what OS version developers use (though obviously CW is not the perfect choice for developing an OOS project, since CW is a commercial app, but that fact still doesn’t make Xcode any better).
It’s a shame – but it seems its CodeWarrior people were just out of luck. They figured PPC is here to stay (a reasonable assumption, especially if Freescale, their parent company is interested in making PPC better and advancing it). So, they sell their x86 compiler (which they owned and was actually pretty good!), to Symbian. And then Apple announces its switching to x86. Go figure.
With CodeWarrior, there was at least some competition to Xcode (although not much since Apple undercut CW by giving Xcode away), so that urged Apple to improve Xcode to make it more attracting to people migrating from CW. Unfortunately, now there’s no longer a need for them to do this: Xcode will be the only choice for Cocoa and Carbon apps (not counting stuff like RealBasic). That’s too bad, hopefully it won’t stagnate even more, and actually continue to improve – there’s great potential in Xcode and it does some things well, but it is very buggy, slow, and unpolished at the same time, and Apple needs to address that.
but it is very buggy, slow, and unpolished at the same time: Excellent FUD!
but it is very buggy, slow, and unpolished at the same time: Excellent FUD!
Care to elaborate why you think that is FUD?
I am currently porting a large application from CW from Xcode, and I fully agree with the original author’s opinion: Xcode is buggy and slow and the workflow is counter-intuitive and unnecessary complicated.
Much as they did with BeOS/x86, Metrowerks could simply offer an IDE for use in conjunction with the GNU toolchain. I cannot say that I blame for not bothering, though.
One thing I forgot to mention, is while CW sold their x86 compiler, they could technically still add support for Universal Binaries into CW, if they wanted to. Obviously, they don’t as Apple has been completely hostile to them, and they figure its better to spend their resources on something more fruitful.
However, were they to decide to add Universal Binaries support, they’d simply need to use gcc for the x86 side, just as Apple does in Xcode, and can continue using their PPC compiler for the PPC side, and link them both together into Mach-0 Universal Binary with Apple’s ld that Xcode also uses. It would be a lot of work to set it all up, but its technically possible, even when they sold their x86 compiler. Though, it seems they don’t see it worthwhile (I mean, if their profits don’t justify it – and I doubt they will when Apple tells all its developers that CodeWarrior is deprecated – then it probably isn’t worthwhile for them – despite having a better product).
Probably Apple and mac developers will use Intel C++ compiler…
yes, all things must pass.
i live in Montreal and Metrowerks was launched in this city, before being moved to Texas in the late 90s.
my brother’s next door neighbor used to work for Metrowerks during the transition to PowerPC, which was happening during the 1992 to 1994 period.
i discussed that transition with him once, and he said it was a wild, exciting time at Metrowerks!
they were a small team of about 8 – 10 programmers back then, and these guys in that room were literally holding the fate of the entire Macintosh platform in their collective hands.
he personnally spent a lot of time helping Adobe’s team port their major apps (Photoshop, Illustrator, etc) to the new PPC architecture.
so long and thanks, Metrowerks, from all Mac users.
That really sucks. xcode is really a GUI wrapper for gcc with some minimal project management thrown in; terrible for developers that aren’t familiar with the unix environment behind the Mac interface.
This will probably be my last CW project:
http://www.funpause.com/atlantis/
(already a big hit sales-wise on Mac!)
They’ve announced their support for MacOS X on Intel. I understand this doesn’t replace CodeWarrior, but if executed properly it’ll nonetheless present a measuring rod for XCode.
Metrowerks didn’t “literally” save Apple’s bacon; it’s a figurative statement. How ’bout a little editing here?
no they ‘literally’ saved apple’s bacon.
It’s in the fridge, it’s slighlty brown, but its also over a decade old, so what do you expect.
any more questions?
They give away one of the best IDE’s ever made and provide tons of documentation. There are plenty of open soruce alternatives. There are more and better Mac apps out now than at any time in it’s history (My first Mac was the 128k in 1984). So tell me again how developers are SO alientated by Apple?
Apple does alienate developers with eternal transitions.
From Mac Toolbox to Carbon. From Quickdraw to Quartz. From CodeWarrior to Xcode. From PPC to x86. From FSRef to Unix paths, from PEF to MachO, from Type/Creator to suffix, from the resource fork to nib files…with all these transitions, when are we supposed to add new features to our apps?
I thought Conan the Grammarian hung out at ./, but as the original submitter (and author of the “saved Apple’s bacon” statement) I’ll bite. By the way, I have a Ph.D. in English.
You are denotatively correct that Metrowerks did not “literally” save Apple’s bacon. First, Apple has to my knowledge never been a meatpacker; they are vendor of computer hardware and software. It follows that Metrowerks would have been unable to “save Apple’s bacon” as there was no bacon to save.
So far, so good. You have proven that my statement was figurative, not literal. However, what you are failing to acknowledge is that the statement “literal” is itself not literal, but figurative. I am stating, in a figurative fashion, that Apple would have been in an extremely difficult, even untenable, position during the PowerPC transition if not for Metrowerks. The use of the word “literally” is sometimes undertaken not as an assertion of fact, as you are suggesting, but as a figurative point of emphasis: a rhetorical turn, if you will, an embellishment, a conclusion of the point with a flourish.
So I am well aware that Metrowerks did not “literally save Apple’s bacon.” Perhaps I should have said “totally.” Less elegant, perhaps, but more clear.
Was someone correcting your grammar?
it should have read “metroworks practically saved apple’s bacon”
Ummm, okay, thanks.
I have been using CodeWarrior on Windows for a long time, and I loved it. CW 8 has suited my style of development way better than every version of VisualStudio I’ve used (VC ’97 was quite good, but it went downwards from there…).
So, when I got a Mac, naturally I tried it there. And I must say: it sucks. Badly. It’s been constantly crashing on me, and in the most ridiculous cases. Like, open an empty file, it crashes. Open a file with the wrong encoding, it crashes. Do anything, it crashes. Plus, while you can do Cocoa development, it always felt like a hack to me.
I’m quite a happy XCode user now, but I still miss CW for Windows. A project window, a no-frills code editor, a build button. Wonderful.
Yeah development on a Mac was much more difficult without CodeWarrior. This may hurt companies like Adobe, Realbasic, etc.
But anyone who didn’t abandon mac-specific development long ago was asking for it. Practically everything on Linux runs just fine on OS X, and there are plenty of free development tools.
CodeWarrior for OSX has been pretty poorly supported for a while now. I bought a student copy of it to tutor a high school student about a year ago, and the debugger would crash on launch immediately. The update feature didn’t work, and I was unable to download updates from their poorly maintained web site. I was totally surprised to hear they were working on a new version. It already looked like it was end of lifed to me, which is the assumption anyone should have made after they were bought by Motorola.
That being said, xCode does need a lot of work. Its buggy, unstable, unpolished and often really slow on large projects. But it gets a bit better every version. If you have bugs/complaints, file them with Apple. They are trying to make their developers happy.
Although Metrowerk’s exit is unfortunate, I can’t say it was unexpected. Ever since Apple began bundling their own devtools with the OS, the writing’s been on the wall. Apple wants full control over their development system, and that’s pretty much all there is to it. Not that MW is blameless either, given the subpar quality of recent releases, and the ever-decreasing amount of resources invested in their Mac products. Still, I at least will miss CodeWarrior.
The funny thing is that I think the guy who wrote Premier wanted to improve it, and had to go to Macromedia to do it… His code ends up at Apple, and they trounce Premier with it. That’s the twisted story I remember.
Apple’s “go it alone” strategy seems to produce good software, and leave a lot of developers in its wake. Think Dan Wood. (Watson/Karelia). This results in a string of new product announcements from Apple, and “we quit” announcements from the competitor. Apple is unmoved! And frankly, after a week or so, so is everyone else.
The tactics, good or bad, seem to work. Apple’s software is getting better. And perhaps the competition will reappear in different forms.
Now if they would just put the power-on button on the keyboard and stop asking me if I “really want to restart”, oh and go steal an old version of Connectix Copy Agent and incorporate that in – for smart copies…
hi you said:
Now if they would just put the power-on button on the keyboard and stop asking me if I “really want to restart”
– i agree about the power-on button.
– if you want to get rid of the ‘do you really want to
restart / shutdown?’ message, hold down the Option key
before selecting the restart / shutdown command in the menu: voila, no more annoying message.
>oh and go steal an old version of Connectix Copy Agent and incorporate that in – for smart copies…
Yes!
I always wandered why nobody (Apple, Microsoft, whatever) did COPY that wanderful copy feature…
I will not forget Code Warrior.
When I was using a Mac years ago (many years) I was a student and could not buy Code Warrior because of the price. So I wrote to them and asked if I could buy, for a cheaper price, an old and used version if they had anything there.
Greg Galanos, their CEO, sent me a letter and OFFERED me a copy of their tool. I have kept the box here and the letter, and even though those days I use gcc under NetBSD, I will never forget this move.
Perhaps I would have given up and moved to something else.
So thank you Greg and thank you Metrowerks.
If I am today able to write code, you have been a big part of it.
([email protected])
I’ve been using the Mac for nearly twenty years now and remember when it seemed as though Code Warrior saved Apple’s hide during the transition from the 68k chip the PowerPC processor. For that I will thank Metroworks and miss them.
As a end user, forgive a possibly dumb question. Can a developer using Code X port their code fairly easily to other platforms?
My thanks to all those who have been making Apple Apps over the years!
Bruce