Poor performance of a GUI is a showstopper bug. It should be, anyway.

If Apple has been shipping betas for 2 decades that do not meaningfully prepare the release candidate for users, something is horribly wrong. They're either not listening to the feedback they receive or they're not giving themselves enough time; both are firmly within Apple's control.

Well, firstly, this is a developer beta. So the target audience are developers that want to get a head start on getting their app(s) ready. So measuring battery performance of those dev betas is dumb.

Also, they do listen to feedback and do gather it. They won't change entire design language now tho.

The parent comment wasn't talking about the developer beta, they were talking about the .0 release. They should use the release candidates as an opportunity to dogfood new solutions instead of shipping an MVP to prod.

Maybe for "Apple", but there's one team that takes performance seriously. The WebKit team has a zero tolerance policy for performance regressions (https://webkit.org/performance/) dating back to the implementation of the Page Load Test in 2002 (Creative Selection, p. 93).

WebKit sounds like the kind of scrappy startup Apple might want to acquire and gain some hard-earned engineering knowledge.

>The WebKit team has a zero tolerance policy for performance regressions

But apparently they still welcome app-crashing bugs and UI-stalling code!

WebKit is the only browser that lags when there is too much logs in devtools console on my M1 mac... Pretty funny.

Maybe we should stop accepting this?

> number of showstopper bugs

Screwing with the battery life on a mobile device would be a showstopper bug if Steve were still around.