How to fix the disastrous new Xcode 15 console | Hacker News Reader

How to fix the disastrous new Xcode 15 console

lapcatsoftware.com

52 pointszeroimpl15 comments

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.

Xcode is consistently the worst IDE, year after year.

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.

Yeah, Android tooling is generally shite as well.

Say what you want about their shortcomings in other areas (and there are many), but Microsoft has almost always had decent tools and documentation.

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.

Agreed. It doesn’t even have decent support for VIM-bindings, which is just table stakes for any IDE or text editor aimed at devs.

Apple hiring former Oracle employees now?

Xcode still a disaster?

Each version is a new type of disaster

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.

Xcode development seems to be very driven by the need to have things to demo at WWDC each year.

As someone who used to work there, I can attest that this description applies to all of Apple's software projects under Craig Federighi.

Am I the only one that thinks the new console is a huge improvement? Basically works like console.app with better filtering options.

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.”

It’s a major improvement. And faster. Structured logging is great. But Optional<String>.none as “” is news and shocking to me.

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).

Reply on news.ycombinator.com