Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I believe that Catalina is the best one for an Intel Mac [that supports it] but for Apple Silicon, I am not sure since I don't have one... Another thing with upgrading is hardware compatibility, specifically peripherals...

Even though MacBook Pro 2015 can be upgraded to Monterey officially, since it does not support all the features, I don't see any point in upgrading to it... Also, I don't understand why installing Big Sur and Monterey takes way longer compared to Catalina and older versions...
 
Apple doesn't need to keep releasing new versions of macOS annually. No one is asking for this. Incidentally, there is no other platform out there that obsoletes third party software as fast as Apple does (and again, they don't need to do this).

Furthermore, have you ever developed software for Apple platforms before? To call those developers lazy when the cards are inherently stacked against them shows that you don't understand just how hostile Apple's platforms are to developers.
I have apps that get updated maybe once every 6-12 months if I'm lucky and still don't have Universal support for Apple's M-series chips and require Rosetta to run. I understand development just fine. This is lazy.
 
I have apps that get updated maybe once every 6-12 months if I'm lucky and still don't have Universal support for Apple's M-series chips and require Rosetta to run. I understand development just fine. This is lazy.
Using apps does not equate to understanding (a) how development works and (b) just how annoying it is to develop for Apple's platforms considering just how much they change every freakin' year.
 
Using apps does not equate to understanding (a) how development works and (b) just how annoying it is to develop for Apple's platforms considering just how much they change every freakin' year.
You seem very angry for absolutely no reason.
 
I believe that Catalina is the best one for an Intel Mac [that supports it] but for Apple Silicon, I am not sure since I don't have one... Another thing with upgrading is hardware compatibility, specifically peripherals...

Even though MacBook Pro 2015 can be upgraded to Monterey officially, since it does not support all the features, I don't see any point in upgrading to it... Also, I don't understand why installing Big Sur and Monterey takes way longer compared to Catalina and older versions...
Big Sur and Monterey were far better on my Intel Macs than Catalina ever was.

Even on my unsupported 2012 i7 mini, Big Sur was probably the smoothest macOS experience I ever had on that machine.
 
I'm actually in a fairly good mood. Though, Apple consumers ragging on developers without recognizing just how rough it is to develop for Apple's platforms is like nails on a chalkboard. ;)
I'm glad you're in a good mood. So good, in fact, that you let small things grind your gears like nails on a chalkboard. Apple's move to their custom silicon was indeed a significant shift, and developers were tasked with updating their apps to fully support these new chips. But three years have passed since the switch, and by now, developers should have had enough time to update their apps to fully support the M-series chips. Apple made the transition process relatively smooth, offering tools, documentation, and support to help developers migrate their codebases.

It is essential for developers to keep their apps up-to-date with the latest technologies to provide the best user experience. Embracing the M-series framework can unlock improved performance, power efficiency, and new capabilities for their apps. Additionally, staying up-to-date with Apple's latest innovations ensures that users can take full advantage of their devices and encourages the adoption of newer hardware.

While there might have been some initial challenges during the transition, such as rewriting code or dealing with compatibility issues, these obstacles should have been addressed by now. As technology evolves rapidly, developers must adapt quickly to meet user expectations and capitalize on the benefits of the latest hardware advancements.

It's fair to expect developers to have completed the transition to Apple's M-series framework by now. By doing so, they can showcase their commitment to providing the best possible experience to users and demonstrate their adaptability to the evolving technology landscape. "It's rough" is not an excuse, I'm sorry. People know full well going into the Apple ecosystem as a developer that Apple has big updates to macOS every year and they've been doing this for decades. They aren't slapped in the face with a big surprise when a new version of macOS comes out every single year. If a developer can't update their app to be compatible with the next version of macOS or iOS, then they're not going to be receiving my money. Period. This is the speed of development. This is what is required in this modern age. If they're not up to the task, that's on them. There aren't any excuses. If you want a slower development process, then be a Windows developer.
 
I'm glad you're in a good mood. So good, in fact, that you let small things grind your gears like nails on a chalkboard. Apple's move to their custom silicon was indeed a significant shift, and developers were tasked with updating their apps to fully support these new chips. But three years have passed since the switch, and by now, developers should have had enough time to update their apps to fully support the M-series chips. Apple made the transition process relatively smooth, offering tools, documentation, and support to help developers migrate their codebases.

It is essential for developers to keep their apps up-to-date with the latest technologies to provide the best user experience. Embracing the M-series framework can unlock improved performance, power efficiency, and new capabilities for their apps. Additionally, staying up-to-date with Apple's latest innovations ensures that users can take full advantage of their devices and encourages the adoption of newer hardware.

While there might have been some initial challenges during the transition, such as rewriting code or dealing with compatibility issues, these obstacles should have been addressed by now. As technology evolves rapidly, developers must adapt quickly to meet user expectations and capitalize on the benefits of the latest hardware advancements.

It's fair to expect developers to have completed the transition to Apple's M-series framework by now. By doing so, they can showcase their commitment to providing the best possible experience to users and demonstrate their adaptability to the evolving technology landscape. "It's rough" is not an excuse, I'm sorry. People know full well going into the Apple ecosystem as a developer that Apple has big updates to macOS every year and they've been doing this for decades. They aren't slapped in the face with a big surprise when a new version of macOS comes out every single year. If a developer can't update their app to be compatible with the next version of macOS or iOS, then they're not going to be receiving my money. Period. This is the speed of development. This is what is required in this modern age. If they're not up to the task, that's on them. There aren't any excuses. If you want a slower development process, then be a Windows developer.
First off, you're assuming that all developers have development teams large enough to keep up with Apple's constant platform reinventions. In reality, this is not the case. The Microsofts and Adobes of the world made the jump with no trouble at all. Why? They're huge conglomerates that have the resources to keep up with Apple's changes. Mom and pop developers? They will struggle. That's not laziness on their part. That's just not having the resources necessary to keep up with Apple's changes. Keeping up with Apple's regularly sweeping changes requires resources. This will inherently push away smaller developers and leave behind only big name developers (which is arguably bad for the platform over the long haul).

The other thing you are discounting is that Apple forced developers to move their code from 32-bit x86 to 64-bit x86 AND THEN ONE YEAR LATER said "oh yeah, now port your apps again to 64-bit ARM". If that doesn't leave a bad taste in your mouth as a developer, I honestly don't know what will.

Also, playing devil's advocate further for developers, Rosetta 2 runs Intel code on your average Apple Silicon Mac FASTER than it did natively on an Intel Mac. While, I'd love for Blizzard to "stop being lazy" and update StarCraft II (let alone all of their other 64-bit Intel, Metal-optimized Mac games, let alone their launcher) to be Intel-native, I fail to see what their incentive for doing so is. That's not "laziness"; that's business. Because, again, these things require resources.

Secondly, you speak to how little you know about the topic of software development, let alone for Apple platforms, by speaking of Apple's documentation, tools, and support as "smooth". It's not. Xcode is a mess and it gets worse and worse each year. I know of not a single developer that enjoys working with it. Yet, it's really the only choice that's provided. Apple is an extremely hostile platform to develop for. And seeing attitudes like the one you have, I can't say I'd be motivated to update my code as often as Apple wants, let alone offer things for this platform at all. Who would?

So, no, your speaking of a community of professionals working a field you are demonstrating a clear lack of understanding of isn't dampening my mood whatsoever. Though, it is completely confounding and I'm imploring you to leave the realm of Apple consumer focused only on their own needs and wants and critically examine the other side of the equation because chalking it up to "lazy developers" doesn't really accomplish anything for anyone, you especially.
 
First off, you're assuming that all developers have development teams large enough to keep up with Apple's constant platform reinventions. In reality, this is not the case. The Microsofts and Adobes of the world made the jump with no trouble at all. Why? They're huge conglomerates that have the resources to keep up with Apple's changes. Mom and pop developers? They will struggle. That's not laziness on their part. That's just not having the resources necessary to keep up with Apple's changes. Keeping up with Apple's regularly sweeping changes requires resources. This will inherently push away smaller developers and leave behind only big name developers (which is arguably bad for the platform over the long haul).

The other thing you are discounting is that Apple forced developers to move their code from 32-bit x86 to 64-bit x86 AND THEN ONE YEAR LATER said "oh yeah, now port your apps again to 64-bit ARM". If that doesn't leave a bad taste in your mouth as a developer, I honestly don't know what will.

Also, playing devil's advocate further for developers, Rosetta 2 runs Intel code on your average Apple Silicon Mac FASTER than it did natively on an Intel Mac. While, I'd love for Blizzard to "stop being lazy" and update StarCraft II (let alone all of their other 64-bit Intel, Metal-optimized Mac games, let alone their launcher) to be Intel-native, I fail to see what their incentive for doing so is. That's not "laziness"; that's business. Because, again, these things require resources.

Secondly, you speak to how little you know about the topic of software development, let alone for Apple platforms, by speaking of Apple's documentation, tools, and support as "smooth". It's not. Xcode is a mess and it gets worse and worse each year. I know of not a single developer that enjoys working with it. Yet, it's really the only choice that's provided. Apple is an extremely hostile platform to develop for. And seeing attitudes like the one you have, I can't say I'd be motivated to update my code as often as Apple wants, let alone offer things for this platform at all. Who would?

So, no, your speaking of a community of professionals working a field you are demonstrating a clear lack of understanding of isn't dampening my mood whatsoever. Though, it is completely confounding and I'm imploring you to leave the realm of Apple consumer focused only on their own needs and wants and critically examine the other side of the equation because chalking it up to "lazy developers" doesn't really accomplish anything for anyone, you especially.
Don't care. Stay current or you won't get my money. That's it.
 
Good luck with that attitude. I think you'll find yourself disappointed.
I actually find myself using apps that are frequently updated that are consistently stable even when new versions of macOS arrive, allowing me to have the latest features of macOS while still enjoying the software I use to make a living. So I'm good, thanks.
 
Hi all;

Is it worth upfrading to Monterey? Please don't laugh as I'm still using Big Sur with no headache.

I have an Anker 7 input device which works just fine and hoping it will still work with Monterey

Really apprecaite your advie here

NO NO NO!

Big Sur is the latest “most stable” OS. I went to Monterrey and quickbooks and several other plug-ins stopped working.

Monterrey IS much better now but I wouldn’t upgrade unless you have software that require it.

I plan on staying Monterrey for a while. I’ve become terrified as each MacOS bring a slew of new headaches and software issues.
 
Personally, I'm sticking with Big Sur until the next round of updates come and confirm that Big Sur is for sure no longer supported. It most likely has already received its last update and I should just move on to Monterey. Soon, I will.
 
Hi all;

Is it worth upfrading to Monterey? Please don't laugh as I'm still using Big Sur with no headache.

I have an Anker 7 input device which works just fine and hoping it will still work with Monterey

Really apprecaite your advie here
Yes! Very happy user (preinstalled in M2 Air).

It’s pretty interesting that Ventura & Sonoma are in the corner while there is still a fully functional and fully compatible old Monterey OS that are still running very well and fast.
 
Last edited:
I'm running macOS Catalina and have no problems or slow downs. I have heard that upgrading to macOS Monterey with Fusion Drive will make your computer run slower. That's one of the reasons I haven't upgraded. Does anyone know if there is any truth to this slow down with Monterey? (See my signature for what I'm running)
16 GB Memory, Processor 4.0 GBz, i7
 
I'm running macOS Catalina and have no problems or slow downs. I have heard that upgrading to macOS Monterey with Fusion Drive will make your computer run slower. That's one of the reasons I haven't upgraded. Does anyone know if there is any truth to this slow down with Monterey? (See my signature for what I'm running)
16 GB Memory, Processor 4.0 GBz, i7
There is a terminal command you can do to separate the fusion drive into two separate drives. I did that and reinstalled the OS on the SSD portion.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.