Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Every company has limited engineering resources and Apple is no different.

Ideally, everything is updated at the same time with no bugs. Realistically, Apple needs to focus on the latest OS and most recent devices.
Every company does not have a $2.8 trillion market cap. Every company is not hoarding cash. Apple has far more than enough resources to hire more people to fix bugs. But Tim Cook is an MBA suit who doesn't care about user experience anywhere near as much as he cares about pleasing his beloved shareholders.
 
Stuck on Catalina. I just do not see why my early 2013 rMBP should be left out of current security updates. If Apple stopped the insane ‘yearly’ new os, it would not be artificially EOL’d (almost)

but I knew this going in…
 
The latest supported consumer version of Windows 10 is 20H2, for which support ends in a couple months, by the way, requires at least a processor released in 2015, seven years ago.

macOS Monterey supports every Mac released since... you guessed it... at least 2015.
My q6600 from 2006 runs windows 10 just fine. Same with my phenom 2 CPUs from 2009. No hacks needed. Also don’t confuse the supported CPU list with what will actually run win10. That last bit is no different than macOS requiring m1 for Monterey as anything below it is not enough to support the full feature set.

Please stop making excuses for apple. the truth is that macOS support is terrible. Open core legacy patcher is great evidence that these older macs can run the latest just fine.
 
Last edited:
Windows users will feel mac owners pain. Many windows PC's are still funcionaly viable, still have very good working hardware but has been rendered useless because Microsoft stopped supporting the OS that ran on the hardware. They had the same choice, carry on using a security vulnerable OS or to ditch the old hardware and purchase something new that worked with the latest security supported OS.
 
And those who cannot legit upgrade past 10.13 are...???


Humming along just fine. With smart browsing/downloading habits, together with a few browser extensions (mainly uBlock Origin + Ghostery) and 'Silent Knight' (to make sure firmware and the like is updated), my old mid-2011 Mini I wiped/refreshed for my fiance here is still more than capable for her light/everyday use.

YMMV though and if you feel the need, then by all means, go ahead and upgrade.

Intego and their ilk are nothing more than purveyors of FUD IMO........that combined with Apple's well-known forced obsolescence makes me highly skeptical when articles like these come out.
 
  • Like
Reactions: B4U
Stuck on Catalina. I just do not see why my early 2013 rMBP should be left out of current security updates. If Apple stopped the insane ‘yearly’ new os, it would not be artificially EOL’d (almost)

but I knew this going in…
The problem is, Apple don't want you using nine year old computers. They stopped charging for OS updates in 2013, consequently they have to force you to upgrade your hardware by making it obsolete. I saw this coming in 2013 when they made Mavericks free, because I remember thinking, so who's paying the devs if the OS updates are free? Of course, the answer is it's still you and me, but via a different method.
 
If owners of macs still using macOS Big Sur and macOS Catalina get attacked then i have no doubt Apple will use some PR bs saying it's the owners fault for not upgrading their hardware to use the latest secuirty fixed macOS
As an owner of such a Mac (late 2013 MacBook Pro, now stranded on Big Sur although I do now also have a 2021 14" M1 Pro MacBook Pro) I do understand that eventually there has to be a cut off for support somewhere, however arbitrary that decision might be. What I find most aggravating are the semi regular popups on the 2013 MBP inviting me to update to Monterey even though it isn't supported on that hardware!

Screenshot 2022-04-07 at 13.21.14.png
 
Windows 10 still gets security Updates and runs on hardware older than 9 years old. Stop making excuses for apple.
No one is making excuses for Apple. When a product whether it's made by Apple, Google, Microsoft, Samsung, reaches end-of-support / end-of-life status, the company is not obligated to provide any updates. As consumers, if we choose to use products that have reached end-of-life / end-of-support status, we accept that risk.
 
Apple is more and more pushing users to use the latest OS.

I doubt this is the reason, it’s most likely a matter of prioritization. They will most likely fix these issues in previous versions of macOS, too.

But imagine the news if they did it the other way around.

Anyway, I’m sure Apple wouldn’t risk security as a way to get people to upgrade. They actually support older systems with security patches longer than most in the industry.
 
Every company has limited engineering resources and Apple is no different.

Ideally, everything is updated at the same time with no bugs. Realistically, Apple needs to focus on the latest OS and most recent devices.
Apple has around 200 billion sitting in a bank. There is no excuse for limited engineering resources.
 
  • Like
Reactions: jakey rolling
Interesting take. I wonder why this is not done with iOS 14 and previous versions as well.
If Gatekeeper worked all the time there wouldn't need to be security updates. iOS doesn't use Gatekeeper because everything is sandboxed and apps have much less access to the system than in macOS.
 


With the release of macOS Monterey 12.3.1 on Thursday, March 31, Apple addressed two critical vulnerabilities that may have been actively exploited in the wild, but as Intego pointed out this week, Apple left macOS Big Sur and macOS Catalina users vulnerable.

macOS-Big-Sur-Feature-Triad.jpg

The macOS Monterey 12.3.1 update fixed a pair of security flaws, including an AppleAVD issue that could allow an application to execute arbitrary code with kernel privileges and an Intel Graphics Driver issue that could allow an application to read kernel memory. Apple said that it was aware of reports that these vulnerabilities "may have been actively exploited," aka there are attacks that use these specific security holes.

Apple often provides security updates for macOS Catalina and macOS Big Sur users alongside macOS Monterey updates to make sure that Mac users who continue to run older operating systems remain protected. Apple has not done so in this case, and there are no security fixes for macOS 11 Big Sur or macOS 10.15 Catalina.

macOS Big Sur and macOS Catalina are still being supported with updates for notable vulnerabilities, so it is not clear why security fixes have not been released. According to Intego, this is the first time that Apple has not released simultaneous security patches for Big Sur and Catalina alongside fixes provided for macOS Monterey.

Big Sur remains vulnerable to CVE-2022-22675 (the AppleAVD bug), while CVE-2022-22674 (an Intel Graphics Driver bug) likely impacts both Big Sur and Catalina, based on research conducted by Intego.

There are some Mac users who choose to remain on Big Sur or Catalina who could install Monterey to get security fixes, but other Mac users have older hardware that is not able to be updated to Monterey, and these users have no way to address the security flaws that are now publicized.

Intego estimates that around 35 percent of Macs in use today could be affected by one or both vulnerabilities, and Apple has not responded to the site's request for an update on when security fixes might come out for Big Sur and Catalina.

Article Link: Apple Fixed Two Actively Exploited Vulnerabilities in macOS 12.3.1 Monterey, But Hasn't Released Updates for Big Sur or Catalina
I’m with Mojave and I need the update. Thanks Apple
 
The latest supported consumer version of Windows 10 is 20H2, for which support ends in a couple months, by the way, requires at least a processor released in 2015, seven years ago.

macOS Monterey supports every Mac released since... you guessed it... at least 2015.
Well gee - I must've not gotten that memo. I have multiple machines currently running Windows 10 21H2 in my household, including a desktop running a 2nd Gen Core i7 and a Dell M3800 laptop (circa 2011 and 2013 respectively).
 
Well gee - I must've not gotten that memo. I have multiple machines currently running Windows 10 21H2 in my household, including a desktop running a 2nd Gen Core i7 and a Dell M3800 laptop (circa 2011 and 2013 respectively).
Yep, my Lenovo Thinkcentre I've been running in my family business since 2013 runs W10 21H2. I get security updates and it's had a SSD swapped in and 16GB of ram added to it. I'll probably replace it when W10 finally gets put out to pasture but until then its more than fine.
I doubt this is the reason, it’s most likely a matter of prioritization. They will most likely fix these issues in previous versions of macOS, too.

But imagine the news if they did it the other way around.

Anyway, I’m sure Apple wouldn’t risk security as a way to get people to upgrade. They actually support older systems with security patches longer than most in the industry.
That last part of your statement is true only IF you are running the latest OS/OSes. I still run Mojave on my 2018 Mac Mini at home because I rely on older 32-Bit applications and plug-ins for my art practice. I don't see the point in spending money or losing access to external hardware because Apple decided to no longer supports 32-Bit.
Windows doesn't look that bad at this point.
 
Apple has around 200 billion sitting in a bank. There is no excuse for limited engineering resources.
As Fred Brooks points out (in The Mythical Man Month) nine women can't have a baby in one month. There's a limit to how effective more personnel are when it comes to solving a software problem and a real point at which more people is a hinderance. Money allows for higher caliber engineers but productivity is always limited.
 
As Fred Brooks points out (in The Mythical Man Month) nine women can't have a baby in one month. There's a limit to how effective more personnel are when it comes to solving a software problem and a real point at which more people is a hinderance. Money allows for higher caliber engineers but productivity is always limited.
Right. Because more money wouldn't at all mean that you could have one set of engineers identify the security problem (which has already happened), and then four more groups of engineers to apply the solution to the last four major versions of the software.

Oh wait a sec. Programming is not at all like giving birth. Funny that.
 
Right. Because more money wouldn't at all mean that you could have one set of engineers identify the security problem (which has already happened), and then four more groups of engineers to apply the solution to the last four major versions of the software.

Oh wait a sec. Programming is not at all like giving birth. Funny that.
Well, it's a little like giving birth. Some problems just aren't divisible. (Also, there's often a lot of screaming and drugs involved.)

To the point though, if you've got a couple of folks who deeply understand the problem (and the fix) it might be that communicating the information required to teams that don't have that understanding takes longer than simply doing the work.

Your experiences might differ but I find that Brooks sums it up well (and, unfortunately, because it's not good news, his advice is usually ignored).
 
  • Like
Reactions: visualseed


Right. Because more money wouldn't at all mean that you could have one set of engineers identify the security problem (which has already happened), and then four more groups of engineers to apply the solution to the last four major versions of the software.

Correct. It wouldn’t. Software engineering teams simply don’t scale that way.
 
To the point though, if you've got a couple of folks who deeply understand the problem (and the fix) it might be that communicating the information required to teams that don't have that understanding takes longer than simply doing the work.
"Doing the work" is updating the libraries affected by the security vulnerability. Unless Apple's software engineering has gone completely off the reservation in the last ten years, these vulns are all part of the same section of code in the same set of libraries (different versions, maybe, but still effectively the same codebase). You don't need multiple groups of engineers who understand the problem. You need one set of engineers who do, and several sets of engineers to find the relevant code in the libraries and update it.

I do agree, there are a lot of engineering problems that aren't "divisible" and can't be more quickly solved by adding engineers to the mix. This isn't one of them. There is a lot of parallel work that can be done here with relatively little more than additional competent bodies.
 
Windows doesn't look that bad at this point.

Good luck with that. :)

Also, while it comes with problems if you rely on specific old apps that don’t get updates, Apple dropping 32bit support was an important move. Windows’ main problem has always been the business requirement to keep backward compatibility - trust me, Microsoft engineers are not too happy about this and it’s definitely holding Windows back.

Apple has announced the 32bit transition a long time ago and developers had several years to update their apps. Honestly, at this point, this is on the devs of the apps you’re using, not Apple.
 
Last edited:
Good luck with that. :)

Also, while it comes with problems if you rely on specific old apps that don’t get updates, Apple dropping 32bit support was an important move. Windows’ main problem has always been the business requirement to keep backward compatibility - trust me, Microsoft engineers are not too happy about this and it’s definitely holding Windows back.

Apple has announced the 32bit transition a long time ago and developers had several years to update their apps. Honestly, at this point, this is on the devs of the apps you’re using, not Apple.
Apps apps apps? What about external hardware? What about plugins?
There is more than hitting a magic button and expecting a 64-bit or Universal application to come from it. Some of my scanners and printers costs more than any Mac they've ever been plugged into, realistically why should any "Pro" support Apple if they drop support for software or hardware because they want planned obsolescence.
 
Apps apps apps? What about external hardware? What about plugins?
There is more than hitting a magic button and expecting a 64-bit or Universal application to come from it. Some of my scanners and printers costs more than any Mac they've ever been plugged into, realistically why should any "Pro" support Apple if they drop support for software or hardware because they want planned obsolescence.
Why should anyone buy expensive peripherals from companies that won't update their drivers? Having said that, I have a pen plotter that predates the Mac that still works fine with a usb to serial dongle. So it is possible.
 
  • Like
Reactions: GalileoSeven
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.