It isn't working for _you_, and you don't know why yet. This isn't yet useful information and doesn't indicate that the entire OS is broken (universally).
But nothing (yet) useful for broader discussion.
Then there is the user 2s. Thats the user with the unsigned software. That download and compiles the random “Show HN” without deep examination. That is experimenting at the lower levels, and might have written some home brewed scripts and apps running on their device.
Generally the user 1s aren’t complaining about updates unless there is an controversial UI or UX change. These are the more reliable reference group for the overall success or failure of an OS update.
User 2s contain all the edge cases configurations that the OS publisher can never fully test for, and generally just aren't reliable evaluators of OS updates.
However overall the title has some truth: Tahoe of all versions fits the most the description of broken. It's the Windows Vista of macOs versions.
> I filed it [on Radar] as FB21983519 in case anyone cares.
rcarmo, please submit a copy to https://openradar.appspot.com
I can understand upgrading for testing purposes, but on my personal machine I've always put it off as long as possible.
It's something to test out in a VM first rather than on real hardware that may actively, permanently thwart downgrading.
Living on the ragged edge for critical personal devices is generally unwise and unnecessary. And I don't think widespread proliferation of accessible betas for consumers is wise from a support perspective.
I'm going to get down-voted for this, but doesn't this describe Apples' target audience? Every year big live streamed events showing the "latest and greatest".
I’m guessing slack would be an obvious red flag on ActivityMonitor if slack was the problem
I had a Linux box that suddenly dies, with no logs indicating what. Turns out that there was some segmentation fault in a service, which killed the computer before it had a chance to write to logs or before the logs were written to disk, somehow, not sure exactly how.
Not until I started sending the logs out to my desktop computer as they happened, could I finally figure out what service was crashing it.
Now macOS is absolutely horrible for headless operations (ask me, just set up one yesterday for signing purposes and it's just... No comment.), but surely there must be some way of macOS to send logs somewhere else, maybe you could try that instead of trying to see it as it happens.
Folks, linux is more stable than any Apple software. I'm going back.
And it feels great.