Re: XCode editor intolerably slow
Re: XCode editor intolerably slow
- Subject: Re: XCode editor intolerably slow
- From: j o a r <email@hidden>
- Date: Thu, 28 Jul 2005 01:56:23 +0200
On 28 jul 2005, at 00.12, David Ewing wrote:
When you see performance issues like these, get a sample of Xcode
and file bugs. We really want to make it snappy.
Really? I have to say that I'm starting to give up on that, after
filing countless performance bug reports for the last two years. If
you look back in the list archives you'll see that I've been an avid
supporter of Xcode, and the idea of filing bug reports - but no more.
It's very apparent that Xcode is not for everyone. It's at least
obvious that you're not supposed to have large projects in Xcode.
Ours is just over 1 M lines of code, but I would expect there to be
significant problems also in much smaller ones.
We have arrived at the point where we need to find a replacement for
Xcode. We've waited long enough for fixes that will most likely never
arrive, because your idea of what's important differ from ours.
It's a bit ironic that it was the development environment on NeXT
that brought us to the platform in the first place - it gave us a
definitive competitive advantage at the time - and now we'll have to
revert back to our primordial command line origins once again...
It's also worth running top and make sure your system's not
swapping. 512MB should be plenty of RAM for Xcode by itself, but if
you're running lots of other apps, memory will be tight, and
performance will suffer.
512 MB might be enough for Xcode alone, but once you load a couple of
large projects it sure isn't. Our developers could never get away
with anything less than 1.5 GB.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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