MACZENTRUM  Great job, Apple!  
(Version 3.2.1)

ILGAZ  Better fix the system requirement to: 10.6 (check rel. notes). Better write in caps: THIS IS NOT 10.5.x compatible version (3.2.1)

You didn't think Apple will be decent enough to fix 10.5 developer tools with updates did you? :)  
(Version 3.2.1)

SHOTGUNWEDDINGS  I had no serious issues with the last update 3.1.2, so I don't expect any from the 3.1.3 release.

Thanks Apple for keep us up to date with all these great developer tools and examples.

5 stars from me all across the board again!  
(Version 3.1.3)

PERSON1229  Why are there things under "Other People Suggest" ?

Nothing beats Xcode.  
(Version 3.1.3)

BRIAN KENDIG  Xcode 3.1.3, with some bugs fixed, was released a few days ago.  
(Version 3.1.2)

ASMEURER  Does anyone know how to change the default shebang line for python scripts? I installed 2.6, but Xcode still wants me to run 2.5.   
(Version 3.1)

BLEE  Java Documentation takes for ever to install because of indexing. I am still indexing the documentation I've check the error logs and no errors have occurred but it's taking an incredibly long time and still going  
(Version 2.3)

ANONYMOUS  XCode (we’re using 2.1 currently) is a usable but flawed IDE for Mac development. Its major shortcomings are:

1. No mouse-driven context sensitivity for variable display in the debugger. The debugger can’t show values of variables you pass the cursor over in your source text. This is really a must-have debugger feature that virtually every other professional debugger has had for years (Metrowerks, Visual Studio, etc.).

2. There are annoying delays when checking/clearing break points and intellisense pop-ups are slow – even on dual G5 workstations.

3. Text editor is slow (slight delays when hitting enter key, typing, etc).

4. Defining configuration sets (ie release vs debug) is overly complicated in how build settings are defined and managed. Apple fiddles with this part of XCode with every release and makes it more and more convoluted.

5. You frequently lose breakpoint markers after compile & run.

6. Debugger stepping is slow.

7. IDE documentation is scant and the HTML based on-line help system just plain sucks (slow, poorly written).

We’ve used XCode for major commercial development and trust me it doesn’t “rock”. It is just barely above the quality that you would expect with free software. It’s less robust than Apple’s ancient MPW, and hardly compares to Microsoft’s Visual Studio especially its substandard debugger.  
(Version 2.2)

HOBIE2987  Xcode is awesome, i prefer it over codewarrior anyday. only problem is if you read from a .dat file or any other type you got to do it by path. they should make it that it will read from the file as long as it follows the same file path. they should make improvements on that but other than that it is awesome and meets my standards for all my future programming needs as a CIS major in college,. way to go apple, kick ass!  
(Version 2.2)

SHINZA.COM  I use Subversion to manage development of Shinza.com. I was very excited to hear about Xcode's imminent Subversion support, but after giving Xcode 1.5 a test drive I am decidedly underwhelmed. I have an existing Subversion server and yet see no way to check out code from the server via Xcode. The SCM documentation is weak and makes no mention about checking out code. If someone has figured out how to use Xcode to check out files from a Subversion server repository, edit them, and then commit them, please let the world know. Until then, I'm going back to BBEdit and SCPlugin.  
(Version 1.5)