3 ms·
I wonder if I'm the only person that thinks that Xcode is the problem, not ObjC. Having experience with C I feel just fine writing code in Objective-C, but only
by fbuilesv 15y ago
I wonder if I'm the only person that thinks that Xcode is the problem, not ObjC. Having experience with C I feel just fine writing code in Objective-C, but only the thought of trying to use Xcode instead of Emacs is painful.
I'd love to know what Eclipse/VS/NetBeans users think about it, maybe it's easier if you're already used to working inside a huge IDE.
- stephth 15y agoyou don't need to use XCode. I keep it open to manage, build, etc, but use textmate to do the editing.
- 5hoom 15y agoNo, you're not the only one. Most of the problems I've hit with iOS development are Xcode-isms. I've recently been sent on a merry hunt to get the built-in git integration from imploding, and the project groups vs folders ambiguity has caused mistakes of the "what actual file is this name pointing too again?" variety (and this in turn leads back to the git integration issues when a file is not where you think it is). It would also be nice if Objective-C++ was a first class citizen with regards to refactoring tools (I understand this might be hard to implement however). Rarely has it been a problem with the actual language itself.
- dbattaglia 15y agoI believe JetBrains have an Obj-C IDE now. Haven't tried it yet but I know they are pretty good at the whole refactoring thing (I use ReSharper at work all the time).
- tomjen3 15y agoI am a fan of Eclipse, but I hate xcode - it hasn't got half of the features it should have and the code completion is just horribly bad.
- n00kie 15y agoxcode - unstable piece of sh*t. Even after so many years it still tends to crash randomly...