Because nobody knows the answer. Hence the opinion.
Let me refine my statement: of large, shipping commercial Mac application software, I’d bet the majority were not developed & shipped using XCode. I hadn’t intended to include every app, large & small, in that statement. Apologies for any confustion.
Yep.
“moving to” is a pretty darned loosed standard, don’t you think? Since the alternative to “moving to” XCode is to run emulated on MacIntel, or abandon the Mac platform altogether, I’d guess pretty much all Mac developers are “moving to” XCode, don’t you think?
Note that “moving to XCode” is not a real big deal – it’s just Apple’s IDE wrapped around gcc, for the most part, and you can certainly use XCode to write generic non-Apple non-Cocoa non-whatever software. It’s certainly not as if there are some uber-elite APIs that only XCode is privvy to, but primarily a case of folks being familiar with the CodeWarrior environment.
Agreed. For smaller apps this isn’t a big deal. For huger codebases, you get to deal with what always happens when moving to a new dev system: the compiler is subtly pickier in different ways than your old one. Not a big deal for smaller apps, but a real pain when you have to reconcile, say, 5 million lines of code. This can take a bit of time, and cause subtle bugs that take time to catch.
There are also myriad other details with switching dev environments for big apps, such as multiple targets/dependancies. Suffice it to say, it’s not just a recompile for a big app, it can be somewhat painful. And when you’re done, your QE gets to test it twice, once for Mac-PPC, once for Mac-Intel.
True. But I’d think that those top 100 developers would include most of the big software. Also, in my experience, most of the small applications I run today on my Mac – ie, not Top 100 developer applications – are written in Cocoa. I don’t make any particular effort to avoid Carbon software, but still most of the icons in my Dock are Cocoa. In fact, all of them are except for the Finder and iTunes.
XCode is really almost six years old. It’s just a renamed version of the developers tools that came with Mac OS X from the beginning.
Though you do raise an interesting question – what happens to RealBASIC programs? Will it be possible for RealBASIC to produce a version that can compile to the Intel Mac OS? Unlike Metrowerks, they have no reason NOT to. They’re a Carbon environment coding program, IIRC – I wonder if they produce Mach-O Carbon programs.
Are we sure? Will CFM Carbon apps run in Rosetta? I was under the impression that they had to be Mach-O.
How do we determine the cut off? All of Apple’s programs are in Xcode. None of Microsoft or Adobe’s programs are, yet. Not sure about FileMaker. Quicken is barely even Carbonized (piece of garbage program). However, most of the way-cool software for Mac OS X certainly is in XCode – it’s almost all Cocoa. All of Omni’s software is Cocoa, for example.
Okay, Metrowerks won’t because of processor politics, but what’s to stop other software development environments from making themselves capable of producing Mactel compatible software? Is there any legal or technical reason why only Apple’s tools can create Cocoa software? Surely one can use other tools to create Mach-O Carbon apps.
I’m not disputing you – you’re probably correct – but how did you determine that?
Actually, Metrowerks has an x86 compiler already for PC. They could fairly easily use that to update Codewarrior for fat fat mac binaries. Last I checked, they hadn’t committed, but I admit I haven’t been paying much attention. Anyone have an update?
[/QUOTE]
Oh, feel free to dispute me. It’s all just hunches and opinion.
But the source is this: Apple is very much an “eat your own dog food” company. Beyond that, virtually all Apple programs are Cocoa. IIRC, only XCode can create Cocoa applications. Is that wrong?
The one major Apple program that’s Carbon is iTunes. Given how well it was running in the demo, I’d imagine it was already Universal. And the key to becoming Universal, according to Steve? Everyone say it with me: “Get to Xcode.”
Yeah, but my thought is that being a wing of Freescale, they’re 1) a bit miffed about the move away from PowerPC and 2) more focused on Freescale’s emerging embedded market.
I asked around a bit re: Metrowerks, here’s what I found out:
[list=][li]They were a no-show at WWDC.[]Apple’s Intel announcment was apparently a complete surprise to them.Most telling: they’d previously sold off thier x86 compiler technology, so they’ve got nothin’ for fat MacIntel binaries.[/list][/li]Codewarrior appears to be dead.
