Re: Xcode's Windows Still Open After Force Quit
Re: Xcode's Windows Still Open After Force Quit
- Subject: Re: Xcode's Windows Still Open After Force Quit
- From: David Frantz <email@hidden>
- Date: Wed, 27 Jul 2011 15:43:28 -0400
I hope somebody from Apple is listening in because I find XCode 4.x to be one of the most frustrating IDEs I've every used. That includes many an IDE for very low volume industrial systems. I just can't understand how opening a simple .plist should bring a machine practically to a halt and crash XCode. The platform (a Early 2008 MBP) isn't that old and frankly runs Eclipse far better than XCode. If Apple thinks I'm going to buy a Mac Pro to run XCode to develop on they are crazy.
I mentioned Eclipse above but honestly I haven't seen any IDE perform as badly as XCode, this includes beta distributions. Due to other software running fine on my MBP I can't blame the hardware. So it comes back to XCode being the problem. It is bad enough that I have to battle with XCode problems while writing my code, it is another thing to have to deal with XCode not being able to handle simple utility issues.
Sent from my iPhone
On Jul 27, 2011, at 9:22 AM, Jeff Kelley <email@hidden> wrote:
> I also wouldn’t go as far as to call it a “piece of crap,” but I will say that Xcode 4.0.x, being garbage-collected (not sure of 4.1.x or higher), was a radical change and probably fueled a lot of Apple’s desire to replace garbage collection with something a bit more sane.
>
> Jeff Kelley
>
> On Jul 27, 2011, at 8:52 AM, David Frantz wrote:
>
>> Does anybody here have the impression that XCode is a piece of crap, going down hill fast? I'm getting extremely frustrated with it and all the various ways there are to crash it. I'm talking XCode 4.1 here which I had high hopes would have been primarily a bug fix.
>>
>> My latest frustration involved trying to use XCode to open and edit a small .plist file. Mind you this was on a machine that was just booted up a few minutes prior and the only reason XCode was even started was to look at a couple of .plist files. XCode couldn't handle that and actually bogged down the machine trying to use a file open dialog. Eventually XCode crashed.
>>
>> Maybe I'm just frustrated but I have higher expectations from Apple. I just can't see how crashing on inspection of a .plist file is acceptable.
>>
>>
>>
>> Sent from my iPad
>>
>> On Jul 27, 2011, at 7:20 AM, Andreas Grosam <email@hidden> wrote:
>>
>>>
>>> On Jul 27, 2011, at 12:37 PM, Dave Keck wrote:
>>>
>>>> Is Xcode still listed as running in Activity Monitor/ps/top? If so,
>>>> you might try 'killall -KILL Xcode'.
>>>
>>> Ah! Xcode is still alive!?
>>>
>>> Killed. :)
>>>
>>> Thanks Dave
>>>
>>>
>>>> I've experienced situations in the past where processes were
>>>> unkillable, even with SIGKILL. (I think the situation involved
>>>> ptrace.) If the situation was recoverable, I think the solution was to
>>>> kill a parent process, so you might try logging out or killing your
>>>> per-user launchd.
>
> _______________________________________________
> 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