Jean-Louis was always pretty honest about stuff. The problem is Apple has too many things going on and only the big stuff gets attention. Take XCode for example, please take it way before I shoot something.
Xcode is the number one reason why I don't do more iOS development. It just takes so much longer to do anything compared to languages that I can edit in a fast, simple text editor and run/test from terminal.
What's so bad about it? I use it for native OSX development with C++ and I have found it very useful, particularly with integration into Instruments for monitoring memory usage, network usage, thread behaviours, as well as the static code analysis for finding dead stores, memory leaks, pointless bits of code etc. (very useful!)
The navigation bar makes navigating the projects easy enough, plus I have added steps in the script sections for builds to package up 3D models/resources into the app, set dylib target references, bundle resources into the executable etc.
Finding where functions are called (callers and callees) from the quick menu is a lifesaver too. I find that I miss the back/forward buttons when I use anything else for editing.
As the project is quite large I could not possibly imagine doing this in a text editor.
I can't imagine not using Xcode for a large Obj-C project either. The UI and tooling is not the issue. In that regard, I love Xcode, it's very helpful. The issue is that it's dog slow on my computer and it eats up all the memory it can get its hands on. That's why I prefer to do non-iOS development, where I don't need to use an IDE.
Comparing it to to dynamic languages is a bit unfair - there's good reasons why iOS apps need to be compiled for the device. The big issue with Xcode for me is not its development speed (I think it has a workflow speed that's not much off from Visual Studio and its profiler is bar none), the problem is that it has become so damn unstable and that certain features are obscurely hidden.
