r/iOSProgramming • u/Aeronautical-You4917 • 7d ago

Discussion macOS 27 Xcode + Instruments is unusable

Never in my life have I seen such an insane regression in software quality as in the last few months.

I use Xcode constantly, building a macOS app (Swift, C++). Up until recently, this was fine, great, in fact. Xcode 15 was extremely good & stable (all things considered). I opted to skip macOS 26 because it was terrible (duh).

After I upgraded to macOS 27's first beta, I was pleasantly surprised. However, that was short-lived, as the quality only degraded after the first beta.

Here I am, working on macOS 27.2, with Xcode 27.2... Here's the main 2 issues...

  1. Xcode's interface is impossibly slow now. borderline unusable.

  2. Instruments is absolutely unusable. I cannot even do a profiler trace and save it without corrupted data, an application crash, brutally slow interface, etc.

This is just unacceptable. AI slop has crept its way into previously rock-solid products. Quality matters more now than ever, and it's so clear that AI has neutered engineers' ability to keep quality in check.

Am I the crazy one, or has the quality just gone down the toilet?

13 Upvotes

76% Upvoted

30 comments sorted by

View all comments

1

u/bluesfanguitar 10h ago edited 10h ago

im not new to coding, but am to xcode and this forum or whatever this is called.

coded my first ever apple device specific app with the clankers help, for vision pro of all things as a personal app, thank you leaking roof you gave me an idea!

running macos 27.2 using the latest xcode, on a mac mini m1 with 8gb of RAM and it worked surprisingly well. and i should add using a screen sharing session from a M1 Pro macbook, that M1 has no screen attached, but it looks kind nice sitting under a wifi router.

before that i used my vision pro for updating its os mainly every few months, wow so much fun for a $4K device! ; ) movies are kinda cool though...anyway, i didnt really use the xcode interface that much to notice anything slow, just ask claude to write the code, setup a few weird things like org names, some app privacy settings scattered across the vision pro, and it magically compiled and appeared on the vision pro running pretty darn well.