1/2
-
@freediverx
in Apple's case, it was switching to Swift as their application level programmung labguage that probably caused those performance issues.
Microsoft's .NET, on the other hand, is solid as a rock. So Windows performace issues are mostly to do with spending 50% or more of every computer's resources on spying on people.
@gullevek @nikitonsky@ramin_hal9001 @gullevek @nikitonsky
For me it's not just the bugs or performance issues, but the way their apps all look and feel like Electron apps now. The UI design, usability, search, consistency, navigation are all bad, and on the Mac, nothing follows Mac conventions anymore.I recall when Mac fans would imagine if we had to choose between using Windows on Mac hardware or macOS on PC hardware. The difficult answer was always the software over the hardware. Today though?
-
1/2
Apple in 2007: here’s 400 videos playing at the same time, with interactive search and real-time animations (via https://t.me/ilyabirman_channel/12350)
@nikitonsky It looks impressive but I can see it's really just 40 long looping gifs tiled 10 times onto primitives. It wouldn't be terribly difficult to do this kind of thing on modern hardware. That would require passion and dedication to a craft but I can see that the modern OS is not living it's best life.
-
@xerz @nikitonsky I have the fear it was just vibe coded
@gullevek @xerz @nikitonsky This interface and SwiftUI both predate widespread LLM usage
-
2/2
Apple in 2026:
-
2/2
Apple in 2026:
@nikitonsky I’ve the 17 pro iPhone and very frequently I’ll open settings.app and the menu icons will take a second to fill. What the hell.
-
2/2
Apple in 2026:
@nikitonsky try changing your wallpaper or screensaver. Borderline unusable. Hangs forever.
-
@nikitonsky Yeah. Software wise it went all to shit. Can’t put my finger on it but I’d say cost cutting for LLM gains
@gullevek @nikitonsky it started long before LLMs, I'd blame the misguided incentive structure in the industry, metric-driven development, all that. Combined with teams needing to keep doing something when all their products have been functionally complete for years.
-
@gullevek @xerz @nikitonsky Apple always has huge performance regressions when they make sweeping UI changes. Just look back at iOS 7.
@Lenora256 @gullevek @xerz @nikitonsky here's a fresh idea: don't do sweeping UI changes
-
@nikitonsky @siracusa I’m not a big “What would Steve do?” guy (in part because he implored us not to be), but he would definitely have been the human shield to protect us from Tahoe if that’s what it took. Such a shame.
Putting all my faith in Ternus & Lemay for a rapid response to the worst of this nonsense.
Jameson, I don't think Jobs would've allowed even the first flat redesign to happen. When the first iOS 7 beta came out, I honestly thought it was a joke. Then I thought, okay, maybe they're serious with this, but sure the icons with all the wrong proportions, as if kids made them, were temporary placeholders. And then all that came out unchanged as the stable release...
-
2/2
Apple in 2026:
@nikitonsky Resizing the windows of some of the new Tahoe apps (Contacts, Phone, Messages, etc.) is slow and drops frames on my 14” M1 MacBook Pro. Sure, it’s not brand new anymore, but it’s still faster than *every Intel Mac ever made*. Come on!
-
2/2
Apple in 2026:
-
2/2
Apple in 2026:
@nikitonsky @siracusa thank you. I’m sick of people saying Tahoe isn’t bad and “you just have to get used to it”.
No it’s bad. As a user, I don’t care what framework is being used or whatever is causing that slow rendering etc. I care about the user experience. Which currently is bad.
-
@freediverx
in Apple's case, it was switching to Swift as their application level programmung labguage that probably caused those performance issues.
Microsoft's .NET, on the other hand, is solid as a rock. So Windows performace issues are mostly to do with spending 50% or more of every computer's resources on spying on people.
@gullevek @nikitonsky@ramin_hal9001 @freediverx @gullevek @nikitonsky Objective-C is still ahead of its time.
-
2/2
Apple in 2026:
-
@gullevek @nikitonsky it started long before LLMs, I'd blame the misguided incentive structure in the industry, metric-driven development, all that. Combined with teams needing to keep doing something when all their products have been functionally complete for years.
@grishka @gullevek @nikitonsky Yeah, making changes to things that work fine, for the sake of work metrics and KPIs.
-
2/2
Apple in 2026:
@nikitonsky For an even stronger effect: open the custom color popover, and *slide* the slider. This creates dozen of color updates, which are queued, and so the preview icons will keep changing colors for *minutes *
-
@Lenora256 @gullevek @xerz @nikitonsky here's a fresh idea: don't do sweeping UI changes
@grishka @gullevek @xerz @nikitonsky I mean, it’s a good idea to do sometimes. I’d rather not still be on skeuomorphic design right now.
-
@nikitonsky omg... glad I didn't upgrade yet
@borkdude @nikitonsky I sat out the Touch Bar, I can sit this crap out too. Shame that containers aren’t as nice before Tahoe, but I can wait, qemu has my back in the meantime.
-
@grishka @gullevek @xerz @nikitonsky I mean, it’s a good idea to do sometimes. I’d rather not still be on skeuomorphic design right now.
@Lenora256 @gullevek @xerz @nikitonsky it's ok to do it together with a major OS update that gives it new graphical capabilities (classic Mac OS -> OS X). It's also ok to do it if you can't fit some genuinely useful feature into the existing design.
However, doing it "just because" is making your users re-learn to do the same things for no reason.
I'd rather have skeuomorphism forever than the modern atrocity where you don't know what anything is until you try interacting with it.
-
@gullevek @nikitonsky macOS 26 is now using realtime SVG graphics for everything. I presume not a lot of time was spent optimizing. So there's your answer.
@xerz @gullevek @nikitonsky well that answers nothing
