Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This a great example of why the release cycle for macOS is messed up. I no longer dare to update to the latest version of macOS until like six months or more have passed from the release date. And when I finally do the upgrade, Apple is pretty much already pushing out the next version of macOS. So yeah, I'm always behind on these macOS versions, but that is because I care more about having everything working than being a ginny pig for Apple's new operating system.

Apple needs to go back to releasing macOS every two years or more. These annual updates have been lacklustre for many years now, and I have felt most of them did not even justify the introduction of a new macOS name. Surely, Apple could bring those tiny updates (like send later in Mail) to Monterey with a simple software update, but no. Everyone must update Ventura to get that one cool feature people might want.

I fondly miss the times of Snow Leopard and Yosemite when the macOS updates were actually impressive and were almost bug-free from the start. Now new macOS updates are kind of meh and okay at their best, and like I said, we need to wait a long time until most of us even dare to update. So how about you Tim skip announcing a new macOS this year and just focus on getting Ventura running well?

I'm with you. I am really sick of the yearly OS updates for MacOS. They are mature products anyways, there just isn't much that isn't gimmicky to add anymore. I'd still be OK with the yearly cadence if they did a tick-tock kind of thing though like Leopard/Snow Leopard where every other year is a Long Term Support version of the OS that focuses on improving under the hood operation and bug fixes. Then people could opt for the latest shiny, or just skip it for the LTS version every other year. Then Apple could almost immediately drop support for the non-LTS version just a year or so after it's out, but should keep supporting the LTS versions for 4 Years or more. They could stretch that out further and I'd still be fine with it.
 
Apple cut them off. What are they supposed to do? The vast majority don't have the ability to zig around Apple's blocks and install Ventura on ($discontinued$) machines that work perfectly fine.
I know the older machine with nvidea cards work great in Mojave using dosdude1 files. Just install on external disk with APFS and apply all updates and then copy APFS to hfs+ internal disk and nice and fast.
 
My top of the line 2009 iMac 27 inch with the i7 is still working like a champ. So, what do I do? Sledgehammer the sucker?
Using dosdude1 you can run Mojave and using opencore legacy patcher works great for Big Sur Monterey and later as long as video card is not and but nvidea or Intel. It does sort of work with amd macs but with limitations.
 
Updates are supposed to give more security and stability, not in Apple's case.

Thank you beta testers
 
On iPad, I go to Settings > General > Software Update. Then I click Learn More and see this:

1676345639164.png


Meanwhile on iPhone, the Learn More text looks like this:

1676345571998.png


Good job, iOS interface team! The Learn More text for iPhone has been like this for the past several iOS versions. Why does Apple want to make their iPhone software update information unreadable?
 
There is a good reason why Safari for Big Sur and Monterey should still have version 16.3 not 16.3.1.

The build numbers of the new Safari for Big Sur and Monterey are in sync with that for Ventura 13.2.1:

Big Sur: 16614.4.6.11.6

Monterey: 17614.4.6.11.6

Ventura: 18614.4.6.11.6

And the version number for Safari for Ventura 13.2.1 is - you guessed it: 16.3, not 16.3.1:

new ventura safari.png


So I reckon the security info at https://support.apple.com/en-us/HT213638 and https://support.apple.com/en-au/HT201222 saying the new Safari for Big Sur and Monterey is 16.3.1 is incorrect and they should be changed to 16.3.

This would be preferable to re-releasing the Safari updates as 16.3.1.
 
Last edited:
  • Like
Reactions: Larsvonhier
I'm with you. I am really sick of the yearly OS updates for MacOS. They are mature products anyways, there just isn't much that isn't gimmicky to add anymore. I'd still be OK with the yearly cadence if they did a tick-tock kind of thing though like Leopard/Snow Leopard where every other year is a Long Term Support version of the OS that focuses on improving under the hood operation and bug fixes. Then people could opt for the latest shiny, or just skip it for the LTS version every other year. Then Apple could almost immediately drop support for the non-LTS version just a year or so after it's out, but should keep supporting the LTS versions for 4 Years or more. They could stretch that out further and I'd still be fine with it.
Can’t arbitrarily discontinue support for perfectly good machines as quickly, when on a two year cycle.
 
  • Like
Reactions: williedigital
I’m gonna ride 15.7 out until the final 16.x update, if not later than that depending on how things are looking. Hoping iOS 17 will be focused on stability and fixes.
Has it been confirmed that the Safari security vulnerability not affecting the version of iOS 15.x ?
 
For most users I'd wait 30 days from now before applying the update so that if there are any breaks then early adopters can report it to Apple and MR without your life being disrupted.

That's what I do... wait for MR users to bleed on my behalf.
 
Alas local network problems are still not fixed in this release. Both with Ventura, I have one Mac I can access and one that I can not. I must switch off, reboot then switch on file sharing again for it to work. Until the next reboot.
 
Using dosdude1 you can run Mojave and using opencore legacy patcher works great for Big Sur Monterey and later as long as video card is not and but nvidea or Intel. It does sort of work with amd macs but with limitations.
It is fully loaded with Radeon HD 4850 video card and 32GB of RAM. 😅
 
  • Sad
Reactions: JosephAW
I'm with you. I am really sick of the yearly OS updates for MacOS. They are mature products anyways, there just isn't much that isn't gimmicky to add anymore.
It seems like a solution (or a convention) looking for a problem. Update OS when you have a really good idea to improve it. Otherwise, do point updates that clean up bugs.
 
  • Like
Reactions: HVDynamo
Updated 12 pro max last night.

Is anyone else having intermittent issues with AirPods Pro 2 cutting out? This seems to be new post-upgrade. It’s very intermittent, but they disconnect for about 3 seconds and then pick back up.
 
  • Like
Reactions: colinwil
I can't even update from macOS 13 to 13.1 or 13.2 on my external drive 😅
I've tried numerous ways (software update, full re-install, from recovery drive), at different times, with different versions (13.1 and 13.2).

Aaaaaaand I ended up throwing up the towel.

View attachment 2158008
Ha. You fool. You think that just because Macs have long supported booting from external drives that they would continue to do so? You've failed to take notice of Apple's new slogan; "Apple. Nope, can't do that!"

(Speaking of which, Apple has removed the ability to initiate Mac updates at the enterprise / edu level, leaving large-scale deployments at risk. We can still update Intel systems, but not AS machines at this point.)
 
  • Like
Reactions: Aquaporin
But, but....

Hasn't Apple been claiming all along that their reason for forcing other browsers to use Webkit was that they claimed Webkit offered better security than other browser engines? Bahahahahahahaha! 🥚on their faces with this one. 😄
Fixing an issue in WebKit doesn’t show its any better or worse than other browsers.
 
Ha. You fool. You think that just because Macs have long supported booting from external drives that they would continue to do so? You've failed to take notice of Apple's new slogan; "Apple. Nope, can't do that!"

(Speaking of which, Apple has removed the ability to initiate Mac updates at the enterprise / edu level, leaving large-scale deployments at risk. We can still update Intel systems, but not AS machines at this point.)
This is a trend in personal computing. Lock down the hardware for security. But also for preservation.
 
Since we have 13.2.1 I guess the Ventura RSR feature was not utilized here - which means the 13.2 RSR beta test for developers must not have gone as expected? The new Ventura RSR update feature is based on the MDM update commands which all Mac IT admins know are only successful around half the time. This quick security fix is exactly what the new RSR update feature was intended for.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.