I finished doing Nukes and paves sometime ago, not sure how long. I doubt I will until I feel I need to, whatever that means really?
I am less and less familiar with the nuts and bolts of the OS’ and frankly that is why I am on Apple in the first place and I finally feel it is doing on Mac what it did on iOS, just worked as they say. I always thought that even with a lot of ‘maintenance’ Macs were excellent relative to anything else by the way. I am, as some of you know, a bit of a ‘small company’ guy, but… there you go!: frankly on computers it isn’t worth the hassle to ‘roll your own’, ‘hack’ or jerry rig. I concede defeat.
Well low maintenece and my beloved DEVONthink 3 Keyboard Maestro and one or two other Mac only apps.
I spend more time on learning RegEx and things that are way more useful than just keeping one’s machine alive as it were. Not sure if others would agree?
I nuke and pave every major release but understand your point, it usually does just work. I also am “less and less familiar” , but am working aggressively to close that gap.
So, I will nuke and pave but only after I get the .ipsw files and can really scrub it out.
I admire your caution. For an anecdotal report, I’ve used it all summer and have had zero problems. I didn’t have to report a single bug on Feedback. It’s been the least buggy OS update I’ve ever experienced.
I always upgrade (and migrate to a new machine or use a Time Machine backup - going back to 2011). I only install from the Mac App Store or Homebrew and keep ~/Library tidy (mdfind -name App). These would also make it easier to erase and reinstall but (forum membership notwithstanding) I’ve got better things to do than configure settings. I have no need to declare bankruptcy every year if I don’t make a mess in the first place.
I just update. My understanding is that nuke and pave isn’t necessary on modern Apple systems and is a legacy from the 90s. I’m glad to see a few other comments here confirming my view. That’s reassuring!
I actually nuked my Mac a year ago for an unrelated reason, so I also know that I don’t want to go through that hassle again unless I have to.
Looks like this might be the last update for my Intel MacBook Pro though. I knew this day was coming, but unfortunately I had to change my office desk and my computer speakers in the same week, so the Apple fund got stripped back to 0. No shiny new Mac for me for a while. (My new desk is an electric adjustable standing desk though and is probably more exciting than a new Mac. That might be heresy in this forum, but the desk is life-changing!! )
Well, having just said that, I thought I’d go over to the Apple website to see how much a new Mac is going to set me back, and it seems like a MacBook Air with M3 does everything my Intel MacBook Pro does, so maybe this purchase isn’t as expensive as I thought
Yes. I ran the 18 and 18.1 on both my m1 iPad Pro and my iPhone 15 pro max. I’m not exaggerating, I can’t recall a single bug that I encountered.
I reported only one strange behavior that appears to now be resolved. After taking a photo on my iPhone, if I clicked the icon in the lower left-hand corner to review the photo, it was out of focus. If I closed the camera and went to the Photos app; however, the photo looked as you would expect it to look. According to my feedback report, there were fewer than 10 other reports of this issue.
As for the other settings, I treat it as an opportunity to look through what’s new and to set things up as I like them. You can miss a lot if you just upgrade. (I only upgrade for the Name Change versions, not the in-betweens.)
Ah, thank you.
I do change a lot of settings there. I wish, those were more automation friendly. defaults write ... is neither intuitive (to me) nor well documented.
You are absolutely right about missing new settings.
I would just prefer to explore those whenever I feel like and not when I feel like I can’t use my computer.
My ideal version of the nuke and reinstall would be going over my config file, cleaning it up, applying it, and then exploring settings.
Edit: Even though I did just upgrade, one of my Alfred workflows just stopped working. Why? I need to accept the Xcode license. I think need to make a light version of my (completely outdated) “new mac”-script for use after upgrading.
I needed to accept the new Xcode license to run Cork, But as I’ve not upgraded to Sequoia it appears unrelated (or at least not directly related, as it is likely the Xcode update was to support the new stuff in Sequoia).
)