Yeah, that's the worst part. They change things around at random.
I've sometimes wondered if Xcode is such a shitshow that they can't keep devs, so each version represents an entirely new team stirring up the crock and trying to make sense out of it.
I work on a multi platform library so I have to use Xcode, Android Studio and Visual Studio regularly all at once. Android Studio has been the worst for me all this time. The IntelliJ interface is better than Xcode but I swear every time I touch Android Studio there is something new broken. Every single time.
Same here and I agree. AS is the one I most fear opening/using. I _love_ IntelliJ, I even have used AppCode to avoid Xcode for fully native stuff but for cross platform stuff my minor use of Xcode is always more pleasant than AS.
I do wonder who is running developer relations at Apple. When I first started coding for iOS their documentation was actually pretty decent in 2012. Now you are lucky to have a new feature fully documented instead of being presented a partial implementation and a few random selections of the possible error states.
nil Objective-C objects, too. Also, logging a signed int in Xcode 15 (for me) ends up being displayed as unsigned if os_log_* or NSLog are used (appears fine in Console.app, though, thankfully).
16 comments
[ 5.6 ms ] story [ 48.3 ms ] threadI've sometimes wondered if Xcode is such a shitshow that they can't keep devs, so each version represents an entirely new team stirring up the crock and trying to make sense out of it.
Say what you want about their shortcomings in other areas (and there are many), but Microsoft has almost always had decent tools and documentation.
Also, this “secret” fix is printed as one of the first log messages. It’s says “hey here’s how to revert back to stdio logging if you need it.”