Xcode 4, despite being "released," is an absolute disaster. I would wait at least a couple of updates (for 4.01) before moving on to it.
Basic functionality is severely compromised. Breakpoints, syntax highlighting, basic functions in the Builder IU interface ... I don’t even know where to start.
Document management, which is the highest design defect in Xcode up to this point, has been changed, but unfortunately has not been fixed. It could be even worse.
At first I had a good impression. Early notes:
More reasonable defaults for debugging hotkeys.
Now in the "File" is now "Close Project"!
You can finally customize sounds for a variety of build and search events using the graphical interface. Nice.
There is a drop-down list that shows the files associated with the one you are editing. This may be useful, but any convenience that it can add is ruined by the fact that there is no quick “analog” button, as before. You need to break through the menu to go from the title to the source or vice versa.
Tabs are upside down starting from the toolbar (WTF). In addition, the “X” indicator for closing is not available on each tab unless you flip the tab. This kind of Easter-egg user interface hides information from the user and should be canceled.
Tabs do not work well for several reasons. Firstly, on one tab there can be two editing panels with different documents; only one of them is displayed on the tab. You also cannot move documents between panels, which you often want to do when you refer to different objects and interfaces. Visual Studio solves both of these problems easily by having separate groups of tabs above each editing area and allowing you to drag and drop documents between two groups.
The second editing panel is always mentioned (and shown on the toolbar) as the "Helper" editor, even if you did not call the helper (which is unclearly indicated by the button of the Batman icon).
View options are in the view where they belong, instead of being placed incorrectly in the Window menu.
If you enter a function call and you use another function call as a parameter, Xcode AutoFill seems to automatically prefer functions whose return type matches the parameter you are filling out. FINE.
But there are many mistakes. So many that it is very difficult to get a job at times.
One particularly annoying error is Xcode's failure to indicate when and where it stopped at a breakpoint. In many cases, it stops and pulls the source file, but there is no execution point. The editor simply shows the top of the file, and nothing happens while going through. The current line is not highlighted, and nowhere does Xcode say “Stopped at a breakpoint”. He just says run.
Unable to sort files in your tree. NONE. Xcode 3 was bad enough, not sorting them automatically, forcing you to go and sort them again and again throughout the life of the project. Now this is not even an option. WTF?
Xcode leaves the editor window littered with errors and messages even after you have fixed the code and recompiled. It turns out that these errors relate to a different goal, even if you never built this goal, and the code that they complain about no longer exists.
Xcode will overwrite your syntax highlighting options for certain types of characters. You can change them again and again, and Xcode will irreversibly overwrite your settings. You can watch how this happens.
THE BUTTON IS NOT "BUILD" IN THE TOOL AND YOU SHOULD NOT ADD ONE. In fact, the toolbar is not customizable at all, and there is only a "Run" button. What if you do not want to run? Yes, you need to find a hotkey.
What did they do with all the extra space on the toolbar? Created the Project-config NARROWER drop-down list. It is so small that it cannot show you the WTF that you are working on. Meanwhile, next to her is a huge strip of empty space. Incredible.
The Xcode team tried to clear up the clutter that was setting up the project by adding the concept of “circuits”. This is basically an improvement, but a buggy. But I don’t have time for this update ...