Re: XCode, next release...
Re: XCode, next release...
- Subject: Re: XCode, next release...
- From: Tony <email@hidden>
- Date: Thu, 6 Oct 2005 16:07:35 +0200
I Agree
Quickdraw (and other carbon-libs) will be removed in 10.5, so we need
a working xcode.
(AVAILABLE_MAC_OS_X_VERSION_10_0_AND_LATER_BUT_DEPRECATED_IN_MAC_OS_X_VE
RSION_10_4;)
We spent 4 months fighting XCode IDE, speed, bugs (and
incompleetnes), still use CW for development.
Speed, our projects take's 8 minutes in CW to build and over 40 in
xcode !!! ( no optimize and for 1 arch )
XCode is crashing all the time, ppc and x86.
Editor is cruel slow (compared with CW)
CodeWarrior converter don't work.
The xcode debugger is really bad (compared with CW)
... etc ... etc ...
Why don't Apple buy CW ?? instead of inventing the wheel again ???
/TH
6 okt 2005 kl. 09.59 skrev Dix Lorenz:
Hi Scott,
Just a reminder to people that technically you should not be
discussing any Xcode 2.2 seeds on this list since the seeds are
covered by an NDA :)
Also, we can't discuss the internals of when upcoming release will
go GM on this list. Just know that there is a lot of goodness in
the next release :)
While I can understand that you will not say when the next release
is coming, try seeing it from our point of view. XCode has bugs.
Lots of them and not only cosmetic ones. They stop me from being
productive, I fight XCode more than my own Code. With Codewarrior
dead and Apple telling us to use XCode, XCode is absolutely crucial
to every single developer out there. XCode has very prominent bugs
in the Debugger, in the Build System, compile times are slow and
distributed builds are very unreliable, linking is abysmal and
CodeSense screws up its index so often it's not even funny and even
at it's best it could be doing a lot more "sensing" about what
completion would make the most sense.
Right now I actually prefer developing on MS Visual Studio 6! At
least I know that the debugger will show me the values of my
variables which every IDE I've used for the last 20 years has done.
Except XCode which might just show me <incomplete type> (for
integers!!!). Code navigation is a lot faster ("Project Symbols"
would help, but it takes 4s to show me the list so I can start
looking for stuff and even then it is not very responsive) and
simple stuff like "which classes derive from this class", "which
classes derive from this class" or "where is this function called"
is just a click away (is it even possible in XCode?).
Any one or two of these I could live with and wait (more or less)
patiently for a fix. All of them together make XCode barely usable
and I count myself lucky that I can do a lot of my development on
my Windows machine (it hurts to say it but there it is).
We, the developers, do not only want the next release of XCode, we
*need* it. Some bugs are so prominent and obvious, they should have
been fixed and released in a small update just a few weeks after
XCode 2.1. I just hope the "lot of goodness in the next release"
refers to fixed bugs and not additional features only some of us
might use.
Just a question: I assume that Apple accompanies Preview Releases
with some kind of Readme and further assuming it would include a
list of known bugs, what does that mean? They are known and will be
fixed in the final release? They are known and might get fixed?
They are known and will be fixed in some release after the one
coming up?
Don't get me wrong: If all the features worked as they should,
XCode would be a very good IDE. As it is, it just shows a lot of
promise...
Greetings,
Dix
_______________________________________________
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
_______________________________________________
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