Im just glad the software dept is finally taking bug fixing and quality seriously, I don't care if there are 10 release canditates
There are many reported and acknowledged open bugs since development last summer. In all my years owning Mac's since 1999 this is by far the worst release - and I worked on OS X 10.4 - 10.6 with then SVP of Engineering Bertrand Serlet (Snow Leopard is still one of the most solid releases I've used).
I'd rather Apple return to 2-3 year release cycles with new beta's every 2 weeks requiring a full system wipe and install as it allowed us to debug the core OS without third party apps and plugin's being possible factors. Serlet stayed on for 10.7 but left over disagreements with Cook regarding OS X becoming a free annual release in order to entice more developers and consumers into the Mac App Store. I'd rather pay $129 for a solid release than a rushed and buggy OS.
Also loathe the iPadOS UI on a Mac. Finder navigation is terrible with a washed out UI - no matter how much I tweaked my MacBook Pro or Mac Pro's displays for contrast, brightness, etc or used Dark Mode, I couldn't adjust to the changes. iPadOS/iOS works best on small touchscreen devices not a workstation or any desktop/laptop. So much wasted space as well.
Because some bugs will be discovered after the final release. And also each release has a scope, so usually, they fix stuff that was planned for the release and stuff that was broken by accident when adding new stuff. And a lot of bugs that require more work and were discovered but were not planned for the release, will be just pushed for the next one.No, not really.
Theres always bugs.
Unless you are staring every final release candidate is perfect, without found bugs.
In which case why have the .X.X releases?
And why is there still bugs after 11.1 final release candidate?
I signed up here to ask this. Every time the display sleeps or plug in I need to rotate 90deg and revert to get 5120 x 1440 for my 49" samsung with my M1 mbp. Very frustrating.Can anyone confirm if this fixes the ultra wide monitor resolution issues to support 4 and 5k ultra wide monitors for the M1 macs?
A-to-the-men!There are many reported and acknowledged open bugs since development last summer. In all my years owning Mac's since 1999 this is by far the worst release - and I worked on OS X 10.4 - 10.6 with then SVP of Engineering Bertrand Serlet (Snow Leopard is still one of the most solid releases I've used).
I'd rather Apple return to 2-3 year release cycles with new beta's every 2 weeks requiring a full system wipe and install as it allowed us to debug the core OS without third party apps and plugin's being possible factors. Serlet stayed on for 10.7 but left over disagreements with Cook regarding OS X becoming a free annual release in order to entice more developers and consumers into the Mac App Store. I'd rather pay $129 for a solid release than a rushed and buggy OS.
Also loathe the iPadOS UI on a Mac. Finder navigation is terrible with a washed out UI - no matter how much I tweaked my MacBook Pro or Mac Pro's displays for contrast, brightness, etc or used Dark Mode, I couldn't adjust to the changes. iPadOS/iOS works best on small touchscreen devices not a workstation or any desktop/laptop. So much wasted space as well.
That’s why they call them candidates.So were the first two RCs essentially more beta versions? Why call them RCs?
Yes. I miss the days where I could just manage my iPhone via iTunes and didn't have to go searching on Finder.Upvote from me, @DinkThifferent. Agree with everything you said, especially now on my M1 MBA. Things seem good and clean, although Music is fundamentally cumbersome and counterintuitive (library, Store, etc.).
Pushing that ball down the field, I'll risk a downvote myself and say I miss the days before they separated Music, Podcasts, and Video into separate apps.
Emphatically agree. Basic bugs like the constant Kernel Panics on reboot are unforgivable.
It's the same.Can anybody using this go into the messages app on the Mac and tell me the version and build number. Hoping it goes up from 14.0 and 6000 found in 11.1
ugggggghhhhhhhh. so many bugs. but maybe just maybe they were lazy enough to fix it and not update the build number.It's the same.
We've had many small bug fixes for MacOS over the years that were a few hundred megabytes in size. We see minor updates to iOS all the time being small downloads of 100MB. Which is why 3GB download suggests a major amount of stuff had to be fixed in what could have been the final release. Why were they even considering calling it a release candidate in the first place?If you find a bug in one line of code in one system file then you often have to fix several other files. Hence they are called ‘dependencies’. Fix a graphics driver? Then you also have to update a bunch of other things. Fix a sound bug? Then update frameworks and firmware and probably some apps too. Etc.
We've had many small bug fixes for MacOS over the years that were a few hundred megabytes in size. We see minor updates to iOS all the time being small downloads of 100MB. Which is why 3GB download suggests a major amount of stuff had to be fixed in what could have been the final release. Why were they even considering calling it a release candidate in the first place?
I'm also kinda salty because nowhere in that 3GB does it fix iCloud tabs not working at all on my M1. They have never worked since day 1 and my intel Macs like to show me open tabs from weeks ago.
Well, that's the thing,... I really do not connect to anything dodgy. Usually, I keep 20-25 tabs open, mostly work-related things like company portal, G suite, Youtube, and sometimes Netflix. And it keeps crashing on average two times a day. Not sure if that came with Big Sur or the new Safari, as I updated them both around the same time.What dodgy websites are you connecting to? I don't think I've ever had Safari crash on me.
Er ... you DO realize that the Qualys security researchers who discovered the bug in sudo (CVE-2021-3156) say it was first introduced in July 2011; and it impacts all versions of sudo from 1.8.2 to 1.8.31p2 and 1.9.0 through 1.9.5p1 on all unix-like operating systems (like Linux, etc). I'd be suprised if Apple is just now becoming concerned.The sudo that ships with RC3 appears to still be vulnerable. It would be weird if they released 11.2 final with a known vulnerability.
Ohh they should be concerned, every major Linux distro has already released a patched version of sudo.Er ... you DO realize that the Qualys security researchers who discovered the bug in sudo (CVE-2021-3156) say it was first introduced in July 2011; and it impacts all versions of sudo from 1.8.2 to 1.8.31p2 and 1.9.0 through 1.9.5p1 on all unix-like operating systems (like Linux, etc). I'd be suprised if Apple is just now becoming concerned.
Furthermore, an attacker would need local access to a vulnerable system in order to exploit the vulnerability. In many instances, this would mitigate the seriousness of the flaw because an adversary that already has access to a system can do a lot of damage with that access.
For sure Apple should be concerned; I’m suggesting that they have known that the patch (1.9.5p2) is now available as you have pointed out. Let’s hope they serve it out or include it in the final release of 11.2. In the meantime all admins need to be careful how they dole out sudo privileges to local users. Cheers!Ohh they should be concerned, every major Linux distro has already released a patched version of sudo.
It might not be a RCE but anything allowing privilege escalation to root is a serious vector of attack.