5 ms·

If the reason for the poll is due to hesitant of using XCode 4, don't. XCode 4 offers so much more there is no reason to stick to 3.

gte910h 15y ago
Other people on your project are still on 3. It USUALLY works, but sometimes it doesn't to share across versions.
to3m 15y ago
Agreed. With the removal of the scripts menu, your eyes no longer need to be assaulted by 2 iconic menu bar titles, and you get to practice your typing. Furthermore, the lack of any even-remotely-useful disassembly window means that people who argue that it's impossible to debug an optimised build can now be right ;) These two features (or lack thereof) sent me running straight back to Xcode 3. Took about 5 minutes, 3 minutes of which was searching for any way of getting at the disassembly window. I suppose I could have worked around the scripts thing if push came to shove. Anyway, there appears to me to be every reason to stick with Xcode 3 rather than Xcode 4, though maybe Xcode 4 might be OK if you're not some kind of freak, as I appear to be.
- paxswill 15y ago
  Something I ran into recently was the removal of remote debugging in Xcode 4. The facilities to do it are there, as that is how debugging iOS devices is run, but the ability to debug remote OS X clients is gone.
jallmann 15y ago
XCode 4... where do I start? It's slow, buggy, unstable, slow, bloated, slow, and Apple yanked a lot of useful features, like plugins. So now there is no easy way to get rid of the trailing whitespace XCode loves to insert. External editor support is also missing, so vim users like me are SOL. It's really slow too. Enough grumbling for now... back to work. In XCode 4. Edit: to qualify my claims. Slow -- Need I say more? I'm on a MacBook, 4GB of ram, pretty standard hardware. I can't even scroll without stuttering. Apple: at least support your own damn baseline. Buggy -- The split view is so broken. And tab titles aren't always updated when switching files, which hugely hinders usability. And it sets CC=llvm-gcc... why, why, why, why?!?! There's more but I don't feel like getting into it. Unstable -- crashes about once a day, more if I'm swapping devices or using Instruments. Bloated -- 10GB? Really? I didn't realize rounded corners and a compiler took up so much space.
- deleted 15y ago
  [deleted]

gte910h 15y ago

Other people on your project are still on 3. It USUALLY works, but sometimes it doesn't to share across versions.

to3m 15y ago

Agreed. With the removal of the scripts menu, your eyes no longer need to be assaulted by 2 iconic menu bar titles, and you get to practice your typing. Furthermore, the lack of any even-remotely-useful disassembly window means that people who argue that it's impossible to debug an optimised build can now be right ;) These two features (or lack thereof) sent me running straight back to Xcode 3. Took about 5 minutes, 3 minutes of which was searching for any way of getting at the disassembly window. I suppose I could have worked around the scripts thing if push came to shove. Anyway, there appears to me to be every reason to stick with Xcode 3 rather than Xcode 4, though maybe Xcode 4 might be OK if you're not some kind of freak, as I appear to be.

paxswill 15y ago
Something I ran into recently was the removal of remote debugging in Xcode 4. The facilities to do it are there, as that is how debugging iOS devices is run, but the ability to debug remote OS X clients is gone.

jallmann 15y ago

XCode 4... where do I start? It's slow, buggy, unstable, slow, bloated, slow, and Apple yanked a lot of useful features, like plugins. So now there is no easy way to get rid of the trailing whitespace XCode loves to insert. External editor support is also missing, so vim users like me are SOL. It's really slow too. Enough grumbling for now... back to work. In XCode 4. Edit: to qualify my claims. Slow -- Need I say more? I'm on a MacBook, 4GB of ram, pretty standard hardware. I can't even scroll without stuttering. Apple: at least support your own damn baseline. Buggy -- The split view is so broken. And tab titles aren't always updated when switching files, which hugely hinders usability. And it sets CC=llvm-gcc... why, why, why, why?!?! There's more but I don't feel like getting into it. Unstable -- crashes about once a day, more if I'm swapping devices or using Instruments. Bloated -- 10GB? Really? I didn't realize rounded corners and a compiler took up so much space.

deleted 15y ago
[deleted]