Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

First I've heard of any issues.. I have done a couple upgrades already with no issue. I'm sure there are some scenarios where it fails, but Sonoma has been out a while with millions of users being prompted constantly to upgrade. Feels like less than a "you're holding it wrong" problem. HN is obv going to bring out the edge cases, but it doesn't seem like the world is on fire with "Sonoma Bricks" by any means.


I use a lot of Apple products but this attitude you're expressing has always annoyed me (because I see it most frequently when it comes to Apple's software and hardware quality). These bugs affect people all the time and are indicative of poor QA. 5 users at a company we provide some software support for (note: we don't control their machines) decided to upgrade their machines and somehow became unbootable just yesterday. Please don't be in denial about Apple's increasingly worse QA. An intern with a checklist could have uncovered these issues.


We have a fleet of several hundred Macs, most are M1/2 at this point. I heard reports of several Macs coming in for support that booted to a black screen after Sonoma's .0 landed. So many that the JAMF team blocked Sonoma until the .1 landed.

Definitely shoddy QA on Apple's part. Also, your sample size is too small. Everyone works differently and it takes a certain set of settings/workflows to trigger this compatibility issue.


Do you dual boot? I've got two bootable OSX partitions on my mac and this hit me when I updated.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: