Should I upgrade to macOS Mojave?

[stevenshaw]

Hi, I own a mid-2014 MPB under High Sierra, which I love. It's not what it used to be, but it's working like a charm!

I was just wondering if I should switch to Mojave, because I'm prompted to do so and because Xcode requires Mojave...

Or will it just slow down my Mac to the point it's too slugish, forcing me to buy the new one (we've already seen that with iPhone).



Thanks for your help, any input appreciated.

 

[maflynn]

Is there any features of Mojave that you need or want? personally if you have a well running machine, don't mess with success. I have a 2012 laptop that I have running HS, and I have no desire to upgrade that as I do think it will slow it down or cause more problems.

 

[retta283]

High Sierra should be fine for a while. I'd stay there until all Mojave updates are out, or even wait and see what the next version brings.

 

[Stephen.R]

In general unless you have a reason not to upgrade, I would say go with it - I ran HS on my 2011 MBP17, and the biggest 'issue' I think I have on Mojave (on a 2018 MBP15 and 2018 Mac mini) is apps not being updated for Dark Mode yet

 

[MSastre]

I did a clean install when I first upgraded my late 2013 rMBP to HS because of the change to AFPS, and now running Mojave 10.14.4 with absolutely no problems whatsoever. I see no reason not to upgrade.

 

[Fishrrman]

OP wrote:
"Hi, I own a mid-2014 MPB under High Sierra, which I love. It's not what it used to be, but it's working like a charm!"

If it ain't broke, don't fix it.
Here's one more vote to just "stay where you are", since everything seems to be still running fine there.

IF you are determined to plunge forward into Mojave, I STRONGLY SUGGEST that you do the following prior to making the move:
1. Download either CarbonCopyCloner or SuperDuper (both are free to download and use for 30 days)
2. Use either CCC or SC to create a bootable clone of your internal drive onto an external drive BEFORE you attempt the upgrade.
3. Set the cloned backup aside for safekeeping.

This way, if something "goes wrong" on you, you can then:
1. Boot from the cloned backup
2. ERASE your internal drive
3. RE-clone the contents of the cloned backup (High Sierra) BACK TO the internal drive.
4. This will get you "back to where you once belonged" with minimal effort.
If you DON'T take this step before upgrading, you may find yourself "up the creek, without a paddle" to get back down!

 

[MSastre]

I was just wondering if I should switch to Mojave, because I'm prompted to do so and because Xcode requires Mojave..

If you are using Xcode and it requires Mojave, there is your reason to upgrade. Mojave runs great for me.

 

[treekram]

Hi, I own a mid-2014 MPB under High Sierra, which I love. It's not what it used to be, but it's working like a charm!

I was just wondering if I should switch to Mojave, because I'm prompted to do so and because Xcode requires Mojave...

Or will it just slow down my Mac to the point it's too slugish, forcing me to buy the new one (we've already seen that with iPhone).



Thanks for your help, any input appreciated.

If you're an active developer using Xcode and making regular app submissions to Apple, you should upgrade to Mojave as support for the latest macOS/iOS versions are many times only available on the Xcode versions which only work on the latest macOS version. If you're using Xcode to do command-line stuff and running make's, or have a more casual usage of Xcode, you can take a more casual approach to upgrading Xcode (and thus the OS).

 

[MisterSavage]

If you are using Xcode and it requires Mojave, there is your reason to upgrade. Mojave runs great for me.

If you're an active developer using Xcode and making regular app submissions to Apple, you should upgrade to Mojave as support for the latest macOS/iOS versions are many times only available on the Xcode versions which only work on the latest macOS version. If you're using Xcode to do command-line stuff and running make's, or have a more casual usage of Xcode, you can take a more casual approach to upgrading Xcode (and thus the OS).

I got to where I couldn't use my iPhone for testing. Xcode complained that my iPhone was running 12.2 and the existing version of Xcode didn't support that. I had to upgrade to Mojave to upgrade Xcode and it did not go well. I am very thankful for Time Machine.

 

[seankeith90]

OP wrote:
"Hi, I own a mid-2014 MPB under High Sierra, which I love. It's not what it used to be, but it's working like a charm!"

If it ain't broke, don't fix it.
Here's one more vote to just "stay where you are", since everything seems to be still running fine there.

IF you are determined to plunge forward into Mojave, I STRONGLY SUGGEST that you do the following prior to making the move:
1. Download either CarbonCopyCloner or SuperDuper (both are free to download and use for 30 days)
2. Use either CCC or SC to create a bootable clone of your internal drive onto an external drive BEFORE you attempt the upgrade.
3. Set the cloned backup aside for safekeeping.

This way, if something "goes wrong" on you, you can then:
1. Boot from the cloned backup
2. ERASE your internal drive
3. RE-clone the contents of the cloned backup (High Sierra) BACK TO the internal drive.
4. This will get you "back to where you once belonged" with minimal effort.
If you DON'T take this step before upgrading, you may find yourself "up the creek, without a paddle" to get back down!

Hi, Cloner apps such as CCC and SuperDuper are able to reinstate back the old OS without any drawbacks?

 

[MSastre]

Hi, Cloner apps such as CCC and SuperDuper are able to reinstate back the old OS without any drawbacks?

Yes, they are exact clones of your system at the time you copied it, including the OS.

 

[maverick28]

Just my 2 cents. The current trend at Apple to remove features is what dried out my patience. As time moves on they axe more and more routinely used functionality. I installed Mojave this morning (the second time in 3 months, BTW) and, apart from such "little" troubles as Migration Assistant failing to "Migrate" System Preferences and all of my apps and documents, I found that they took out Jabber/Hangouts/Gtalk integration from Messages. So, my solemn congratulations to all of you that depend on reaching out to your friends, colleagues and co-workers who don't have Macs. I'd understand if they did that with some obscure barely used IM service but to cut off the cord to Hangouts is beyond me. Apple really knows how to make people hate them.
There're some slight performance enhancements here and there that were desirable since High Sierra at times behaves like crap, especially, regarding full-screen transformation animations, graphical glitches. But other than that Mojave is a giant step back not forth.
Some UI decisions, like those in Safari - reducing Top Sites to a collection of Web-icons, removing bookmarks pane - are extremely unfriendly, illogical and outright dumb.

If everything aforementioned is important to you - DO NOT upgrade to Mojave.

 

[M3Stang]

I got to where I couldn't use my iPhone for testing. Xcode complained that my iPhone was running 12.2 and the existing version of Xcode didn't support that. I had to upgrade to Mojave to upgrade Xcode and it did not go well. I am very thankful for Time Machine.

I ran into this issue as well, so I just located the device support files for iOS 12.4 and dropped them into the device support folder in Xcode. Now I can run my apps on my iOS 12.4 device from Xcode 10.1 (The newest one that works with high Sierra). Maybe one day I will buy a new/newer Mac, but finding a decade old one for under $100 was what I did and it allowed me to see if I even like Xcode, so had to do this workaround. Probably wouldn't do this in a production environment.

 

[MisterSavage]

I ran into this issue as well, so I just located the device support files for iOS 12.4 and dropped them into the device support folder in Xcode. Now I can run my apps on my iOS 12.4 device from Xcode 10.1 (The newest one that works with high Sierra). Maybe one day I will buy a new/newer Mac, but finding a decade old one for under $100 was what I did and it allowed me to see if I even like Xcode, so had to do this workaround. Probably wouldn't do this in a production environment.

Nice! I didn't know that was a work-around.

 

[The Hammer]

OP wrote:
"Hi, I own a mid-2014 MPB under High Sierra, which I love. It's not what it used to be, but it's working like a charm!"

If it ain't broke, don't fix it.
Here's one more vote to just "stay where you are", since everything seems to be still running fine there.

IF you are determined to plunge forward into Mojave, I STRONGLY SUGGEST that you do the following prior to making the move:
1. Download either CarbonCopyCloner or SuperDuper (both are free to download and use for 30 days)
2. Use either CCC or SC to create a bootable clone of your internal drive onto an external drive BEFORE you attempt the upgrade.
3. Set the cloned backup aside for safekeeping.

This way, if something "goes wrong" on you, you can then:
1. Boot from the cloned backup
2. ERASE your internal drive
3. RE-clone the contents of the cloned backup (High Sierra) BACK TO the internal drive.
4. This will get you "back to where you once belonged" with minimal effort.
If you DON'T take this step before upgrading, you may find yourself "up the creek, without a paddle" to get back down!

But SuperDuper doesn't clone the recovery partion correct?