Neo, which do you want to take - the blue pill, or the red pill?
Take the blue pill, Neo, and you will be in a world where everything
works, where it is easy to view the disassembly of your sources and
even trace through them. Where cross-platform compilation is a breeze.
Where CVS integration works. That is the world of Codewarrior, a
world where there is no hurt, no pain.
Take the red pill and welcome to the world of deadline releases -
where unfinished, bug-ridden software is the order of the day. A world
where GDB gets fried by spurious 'EXC_KERN_BAD_ACCESS' exceptions,
where many menu items are greyed out where they did not have time to
finalise that particular bit of the program. They call this world
Xcode, where the gloves are off, the reality of milestones and
programmers forced to release unfinished work apparent.
Take a look at this list, Neo, see the number of posts regarding
missing functionality and bugs. Now compare to other lists and see the
ratio here is much greater.
Xcode is unfinished and has bugs. CodeWarrior works.
I personally used CodeWarrior until I couldn't afford it, so switched
to ProjectBuilder. Then Xcode. Mistake. It's not finished. If your
livelihood depends on it, stay with what you have if it works, then
wait until this list gets only a handful of posts - then you will know
when utopia has arrived.
On 28 Nov 2003, at 06:01, email@hidden wrote:
Date: Thu, 27 Nov 2003 17:22:50 EST
Subject: XCode or CodeWarrior 9
I'm using CodeWarrior 9 for making C++ Mach-O Carbon apps and I was
of switching to XCode instead of upgrading to CW 10 when it comes out.
not using PowerPlant or PPX so I'm not tied to CodeWarrior. Any major
drawbacks? How about the quality of code the compiler makes (speed,
Also is there a way to compare folders and files?
Death, taxes and Microsoft. If you put it that way, the first two
don't seem so bad.
xcode-users mailing list | email@hidden
Do not post admin requests to the list. They will be ignored.