A lot of this is a repeat of weird issues that we saw 8(!) years ago with OSX Lion. Perhaps I'm off the mark here, but I strongly suspect there's lack of a proper manual QA team at Apple. QA at most so-called "modern" companies these days has turned into overly fetishising automated testing. Automation is valuable, but crucially also leads to situations where the least-common-denominator situations get tested since i…
Yeah, I think so.
Apple's apps have always been terrible, and it seems weird because their Mac OS (though of course buggy in absolute terms) has, for almost 20 years, far outshined any other desktop computing OS of similar complexity (meaning, basically, Windows and Ubuntu and equivalent Linux-plus-all-basic-apps type distros).
I think this is a side effect of their silo culture. App teams are tiny, often one person, and they work in permanent stealth mode. Then they finally release a developer preview, which includes the core OS plus like a hundred app releases.
Suddenly, they have thousands of beta testers: Mac developers paying Apple for the privilege. I've been one for the past 20 years or so. But we don't have time to file bugs (especially through their shitty, rude Radar system, although it's recently finally gotten... um, marginally less shitty). We spend our bug-filing time on the OS deficiencies that are fucking up our own applications.
So the OS itself gets stress tested by thousands of developers, whereas none of us really gives a shit about the app collection that will ship alongside the OS.
E.g., relevant to this issue: thousands and thousands of developers install every OS release and beat on it, but almost none of us would expose our actual email accounts to some developer preview release of Mail.app. We'd just use a different machine, or use webmail for a while while working with the new OS.
So the apps themselves actually get released with pretty minimal real user testing.