macOS Sequoia 15.0 - Is it "Safe"/"Worth" updating from Sonoma 14.7 on Macbook Pro 13" M1 2020?

Just updated to the latest Sonoma version, 14.7. (Always a crap shoot, right, when updating...)


Have a Macbook Pro 13" M1 2020, and I am heavily invested in Google Chrome at this point, with no plans to transition everything (bookmarks, tab grouping history, etc.) to the Safari browser environment. "Settings" is asking on the regular if I want to update this machine. Have read other posts in this forum related to Macbook Air and issues with Sequoia 15...


I am not heavily into content creation or graphics design; I use the Macbook mainly for bookkeeping, spreadsheets, banking business, and correspondence work.


My question is a simple one:


What's the skinny thus far on Sequoia 15.0 running on Macbook Pro 13, M1, 2020, or similar architecture in this series? Is it "safe"? Is it "worth" it? Am I "missing out" if I refrain, and stay with Sonoma right now?


Thanks for weighing in!

MacBook Pro 13″, macOS 14.7

Posted on Sep 27, 2024 12:01 PM

Reply
Question marked as Top-ranking reply

Posted on Sep 27, 2024 1:16 PM

There is no need to rush to upgrade an OS to the next major version. In fact it is usually best to hold off until you have researched & tested your setup with the new OS. I never upgrade to a new major version of any OS until after at least the first update patch. I'm in fact still on macOS 13.x Ventura since I have no need for Sonoma or Sequoia.


Research by checking out the Apple forums here, especially the Sequoia forum to see what issues people are talking about, perhaps even some fan forum sites if you have any you follow. Keep in mind the majority of issues people report here tend to be associated with unnecessary third party software which are known to interfere with the normal operation of macOS (anti-virus apps, cleaning apps, optimizer apps, security software).


Also check with the developer's of all the third party software you use to make sure their apps are fully compatible with the new OS....this includes any plug-ins or extensions that you utilize. If those developers also have forums, then check them out to see what issues the early adopters are reporting. Keep in mind some third party developers may take weeks or months before updating their apps to be fully compatible with a new OS (some have been known to take a year).


Then there is the research part where you perform the tests yourself by testing the new OS yourself. This latter option will provide you with the best results since the online research is only a very rough guide for what you may encounter.


There are several ways to test out the new OS yourself:

  • Install Sequoia into a new APFS volume assuming you have enough Free storage space (minimum 80GB just for the OS without any third party apps)
  • Install Sequoia to an external drive (speeds of external SSDs vary greatly)
  • Have a second backup computer which you can use for testing & emergencies


All three of these options allow you to dual boot so that you can continue working with your current setup while testing out the new OS to confirm whether there are any issues. Once you are sure everything is fine, then upgrade the OS on your main boot volume. If you chose option#1, then you can safely delete the newly created APFS volume to free up the storage space (first make sure to change the default Startup Disk in System Settings).


It is best to test everything for yourself since everybody's setup is completely different even if they are using the computer & OS for the exact same things. All it takes is one piece of hardware, or one plugin that you may use which could make a difference from success or failure with the upgrade.


Most important......always have frequent and regular backups of your computer and all external media (including the cloud) since there are a lot more new ways to permanently lose access to the data on the internal SSD due to all the hardware, software, and security changes of the more recent Macs.

36 replies

Sep 27, 2024 6:02 PM in response to Yer_Man

Thanks very much for your response, complete with valid reality checks.


I am in my 70's now, and happily retired -- from a lengthy IT career actually, spanning from 1981 until the mid aughts, and spent almost entirely in the field and "hands on"). These days I don't really stay much more "informed" about tech than I need to be in order to use the few devices and tools I depend on in daily life. I readily admit I am very much of an if it ain't broke, don't fix it person with most things, and that includes tech stuff. So I suppose that puts me in the "waiting" category with major OS upgrades. Patch updates, not so much. I do those as they come down the pike. I'm more cautious with jumps from one OS release to the next though. If/when I do make that jump it's always and only preceded by a full backup of HD and cloud data. (A "fall back" habit from my IT days, I suppose.)


Perhaps my nomenclature in the OP was amiss, though my intentions were sound: to have a discussion and gain consensus.


Yes, "always back up first". Better to be cautious than become a cautionary tale. And I think that's also prudent advice with most things, in IT and in life.


Thanks again. Your points and advice are well put, and well taken here.

Oct 16, 2024 5:03 PM in response to Barney-15E

Great to hear you haven't had any issues with your apps after upgrading. Aside from updates that are focused around architecture transitons (e.g. Mojave > Catalina, Intel > Apple Silicone), that's usually how it goes for most people, especially with the everyday GUI apps we all use. These apps rely on higher-level macOS APIs that Apple mostly keeps stable and backward-compatible. Since they're sandboxed, they don't mess directly with the core system or depend on system-level stuff, so they're less likely to break during upgrades.


But when it comes to command-line tools like Homebrew or Xcode's CLI utilities, they dig much deeper into the operating system. System Integrity Protection limits what parts of the system these tools can change, and any tweaks Apple makes can throw off tools that need access to specific system directories. With frequent updates to compilers and SDKs, CLI tools have to constantly adapt. If they're using outdated compilers or frameworks that have been deprecated, they'll break until they're updated. These tools also handle dependencies that often need rebuilding or recompiling for the new macOS version.


This means developers and users who rely on CLI tools face ongoing challenges with each macOS release. While most folks won't need to think about this, it's a common concern for anyone depending on a CLI environment whenever a new version comes out.

Dec 5, 2024 4:01 AM in response to raymondjiii

It's not worth the risk

What risk? I installed the beta on two Max and had no problems with it. I don’t install crapware on my Macs, so I suppose if you must install crapware, there is some risk.


i’m not sure what UI Bugs you’re talking about in music. I don’t spend much time with it. I turn it on and hit play and that’s about it so not sure I’d find any UI Bugs if any existed.

Dec 5, 2024 5:32 PM in response to Barney-15E

Please don't mix your nonsense up. Crapware and the Music app are 2 different things. Data science in that I install a lot of modeling, python, R, tensor based software - it's not crapware but it DOES require the kernel to be stable. Why would I tell Apple about these Music bugs are that naive that you think they would actually fix them? What did P.T. Barnum used to say.

Dec 5, 2024 8:04 PM in response to raymondjiii

raymondjiii wrote:

Please don't mix your nonsense up. Crapware and the Music app are 2 different things. Data science in that I install a lot of modeling, python, R, tensor based software - it's not crapware but it DOES require the kernel to be stable. Why would I tell Apple about these Music bugs are that naive that you think they would actually fix them? What did P.T. Barnum used to say.

I install Python, R, R Studio, Autodesk Fusion. Never had a problem with any of them. It is obvious some developers know how to write software that doesn’t try to sneak around in the undocumented bowels of the OS, not caring if their customers are inconvenienced by their software crashing when the OS changes. Use the former, avoid the latter, and there is no risk.


You are the only one conflating the two. I just wondered how you found tons of “UI bugs” when I didn’t notice even one. Sure, I have a very small sample, but surely if there were tons the probability of all of them not appearing during my time using them would be low. As tonnage refers to weight, I’m not sure I know how many “UI bugs” make up either a long or short ton. It is therefore difficult to devise the proper test statistic to use to determine the expected number of bugs I should have observed during my time using the Music app.

Dec 5, 2024 8:23 PM in response to Barney-15E

Sigh...try this...even you should be able to handle this one. Open an album (if you actually have any) where the listed tracks exceeds the open page - that is, you have to use the scroll bar to see all of the tracks on album. Let's say this artist put out a live album and you found (via the artist's website or wherever) that each song was recorded on a different date in a different venue. You now have the list of dates and locations and you want to edit each song with the date and location information. Right click on the first song and make your edits to the song track (put date and location at the end) or for simplicity sake - just put an "X" at the end of the track name; you can always undo it. After you edit the first song use the nice little arrow in the same dialog box to go to the next song, make your edit and keep going for each song. What happens when you get to the end? The screen is screwed up. You have to back out go to some other view and search for the album again. Now someone as bright as you would say, well I would never need to edit such a thing! But, alas, nobody cares what you think, the point is that this is what is known as a software defect and poor quality. That is, this is not how it is supposed to work. I spend a lot of time in the app, I have over 12k physical albums, published, mastered and re-mastered from various countries. I have a lot invested in my music collection. As such, I spend a lot of time in the app. I am not a simpleton with a lack of music taste that "just hits play". There are a number of Search related bugs, albums that import fine one day and then days later they magically split into two different albums - same name, same artist (this is a very well known bug, been there since day 1, there's a work-around for it but did Apple fix it? Apparently not.) How about this one, you want to update the correct or maybe just a better version of the artwork. This is a very common problem, when you import a disc Apple gives you the worst possible artwork - sometimes it is not even by the correct band. Your artwork library has 20k plus files of various resolutions, you go to change to artwork, open up your art work directory and what happens?...You'll be opening Activity Monitor and force quitting a few processes to get the Music app working again. There is a very large list. Just because "you didn't see it" doesn't mean it doesn't exist. Brightness is not something in your list of characteristics.


Sneak around in the undocumented bowels of the OS ? I mean come on now, some python packages are compiled with C but I mean come-on how do public open-source python packages "go to the bowels of the OS" - they don't! I have 16 cores on this box and I want every single one of them chugging away at my model - I think that's a pretty simple thing to ask for. Even a simpleton would have to agree.

Dec 6, 2024 1:17 AM in response to raymondjiii

Sneak around in the undocumented bowels of the OS ? I mean come on now, some python packages are compiled with C but I mean come-on how do public open-source python packages "go to the bowels of the OS" - they don't! I have 16 cores on this box and I want every single one of them chugging away at my model - I think that's a pretty simple thing to ask for. Even a simpleton would have to agree.

Your reading comprehension seems a tad low. I listed Python as functioning without issue. Are you having issues with it? I don’t use any of the ‘condas and I install it using precompiled binaries (never homebrew).

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

macOS Sequoia 15.0 - Is it "Safe"/"Worth" updating from Sonoma 14.7 on Macbook Pro 13" M1 2020?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.