[forgingahead]

My expectation for user behaviour is that users, regardless of self-identified tech competency, shouldn't upgrade their OS on the first day of a new release. I find that there's nothing that one can miss out on with a new release.

[seniorivn]

what's the point of a release date if it's not ready? os upgrades do fail, and you better backup before you upgrade, but if it's released, than it means it's ready

[ben_w]

Conversely, I’ve been looking at release notes and — with the exception of security patches and needing the latest version of Xcode for my job — I’ve not actually seen any positive benefit to upgrading since the versions were named after cats rather than places.

On the plus side, at least the most recent security update no longer had me listening to auto-playing YouTube videos in the front tab of Chrome before I even saw the login prompt: https://www.youtube.com/watch?v=LVvu94g3iq0

On the down side, the latest security update decided to spontaneously start playing the YouTube video in the front tab of Chrome about 15 minutes ago when my laptop went into screensaver…

[concinds]

> On the plus side, at least the most recent security update no longer had me listening to auto-playing YouTube videos in the front tab of Chrome before I even saw the login prompt: https://www.youtube.com/watch?v=LVvu94g3iq0

I had a similar problem, but with resuming from hibernation after the battery goes to 0. When you have FileVault on, that brings you back to the login screen; but Chrome videos started playing instantly. A horrific bug since you can't pause or mute it for a good 10 seconds until you get back to your desktop. Many people have probably been harmed by this bug, depending on what video they were watching last.

[concinds]

Could you share if FileVault was active when this happened to you? I believe the disk is supposed to remain encrypted before you log in, so I can't see how this would have happened on a reboot (or update install) without FileVault being off.

[ben_w]

FileVault was inactive at the time I recorded that, though I still don’t expect this behaviour regardless of file system encryption.

[beagle3]

From my perspective, it means it has been deemed ready for fresh installs — which aren’t uncommon. They have, especially with Apple, fewer configurations to test.

But the probability that they got a good enough sample for system upgrade is very small. Systems that have been in use— especially for a few years — tend to diverge widely.

The users who upgrade should wait unless they are willing to risk the small but not negligible probability that the upgrade will Bork their system.

[hnarn]

> From my perspective, it means it has been deemed ready for fresh installs

I don't think you'll find many "normal" people (i.e. non-developers) that agree with you on that definition.

[beagle3]

Indeed. And those people used to come to me for help when they upgraded their windows prematurely.

[joshspankit]

That used to be the case before everything was connected to the internet: devs would agonize about making sure there were no bugs, because once it was out it was out of their hands.

Games were especially nerve-wracking because a single show-stopping bug could bankrupt the entire company, but I digress.

Now, it’s “Get enough working code out the door so that we can sell copies! We can patch it if we need to!”

[megous]

Software is never ready. It just has some local minimum of known issues.