Re: Codewarrior vs XCode
Re: Codewarrior vs XCode
- Subject: Re: Codewarrior vs XCode
- From: Nick Zitzmann <email@hidden>
- Date: Sat, 17 Sep 2005 15:44:29 -0600
On Sep 17, 2005, at 2:51 PM, Turtle Creek Software wrote:
Seems like there are many angry posts about various XCode flaws. I
suspect the background to that is that many Mac developers have been
using CodeWarrior for years, and are highly productive on a familiar
(and generally quite elegant) interface.
Not for me. I'm a little bit frustrated about how every new version
of Xcode introduces some new features and/or fixes some bugs, and
then breaks things that used to work. For example, shell script build
phases worked correctly in PB 2.1, but were broken in native targets
in Xcode 1.0. Or how the Jaguar SDK shipped with Xcode 1.0 had the
correct CoreAudio headers, but the Jaguar SDK shipped with Xcode 1.2
didn't.
If you'd like Xcode to look like CodeWarrior, then you can turn on
the condensed interface, which is what I've done.
Probably a lot of developers have not even started to consider a
switch
yet.
I switched from CodeWarrior Pro to Project Builder 1 a long time ago,
because PB could build Mach-O binaries long before CodeWarrior could.
I didn't think CFM Carbon would stay around forever. I was correct.
Remember, many of us are old-time Mac folks who spent YEARS arguing
with the DOS majority, saying that drag and drop was so much easier
than typing something stupid like "otool -L <library name.dylib>" into
a command line. Oops wait a minute, that's OSX not MS-DOS.
Welcome to the real world. I always wished the pre-OS X system
releases had a command line, because for me at least, there are a
number of tasks I perform that I can accomplish more easily with a
command line than with a GUI. Development is one of them; it's easier
to type "cvs update ; xcodebuild -alltargets" than it is to give a
GUI client a command to update, wait for the process to finish, click
on the hammer toolbar item, wait for the build to finish, choose the
next target, click on the hammer toolbar item, ...
And now
the majority platform doesn't have a C:/ prompt in sight.
That's not true; all versions of Windows NT, even XP and Server 2003,
have a command line. And most system tasks don't require it, just
like most tasks on OS X don't require the Terminal app.
PLEASE, humor us old Mac fogies and let us have a simple-minded GUI
when we are programming.
What's the problem with Xcode's UI? You haven't told us anything.
I've been using Macs since System 6, and the only problem I have with
Xcode's UI is it's not possible to edit framework header settings in
condensed mode. The only thing I find frustrating about Xcode is the
breakage I mentioned above.
Nick Zitzmann
<http://seiryu.home.comcast.net/>
S/MIME signature available upon request
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden