Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Great! Get rid of legacy bloat! However I feel my 2011 17” MacBook Pro has reached the end of line as far as macOS updates. High Sierra is the end of the line if I were a gambling man.
 
I wonder why Apple has such a fetish for phasing out 32-bit code.

The CPU has NO PROBLEM executing 32-bit code, and there isn't even a performance hit in doing so. There's no real solid reason to discontinue 32-bit support. This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, and expose them to security vulnerabilities for no good reason at all.
FCP 7 is keeping me on Sierra for now.
 
Great! Get rid of legacy bloat! However I feel my 2011 17” MacBook Pro has reached the end of line as far as macOS updates. High Sierra is the end of the line if I were a gambling man.

Surprised the GPU hasn't given up on life yet.

FCP 7 is keeping me on Sierra for now.

That still works on Sierra?! Wow.... I really think you ought to make the move to X, Premiere, Avid or DaVinci though. They're all good NLEs. 7 just isn't up to snuff anymore.
People complained a lot in the beginning of X' life, but it's actually a brillant NLE at this point.
Premiere will feel relatively similar to FCP 7 and a lot of people say it's what FCP 7 would be if Apple didn't change direction with X. Avid is Hollywood's classic and it half expects you to come straight from cutting film rolls with scissors. And DaVinci is the newest player in the pro NLE space. Black Magic is the undisputed king of the colourists' workflows, but with the newer versions of Resolve (DaVinci), editors can now move comfortably to the software as well. And it's really fast. Competing with FCPX on speed. (Both use Metal 2). Premiere loses big time on speed. Then again, coming from FCP 7, anything is blazing.
[doublepost=1516824847][/doublepost]
No, that's not how it works. macOS is already 64-bit and has been for a long time; if you have 4GB then you have 4GB.


I think what the comment says is that he/she has a MacBook that came with 4GB of RAM, but one of the sticks is broken, so it's only 2GB. I don't know how it relates to the 64-bit thing.
 
It's pretty easy to find which apps are 32-bit using Activity Monitor. On the CPU tab, right-click on the headers and select "Kind." Then just click that column to sort. Looks like Adobe and LogMeIn have some work to do on my side ...
 

Attachments

  • Screen Shot.png
    Screen Shot.png
    446.8 KB · Views: 402
  • Like
Reactions: idunn
Crappy. I have scores of vintage apps that have no modern equivalents that I use regularly that will be nuked.

Sucks Apple.
 
It's pretty easy to find which apps are 32-bit using Activity Monitor. On the CPU tab, right-click on the headers and select "Kind." Then just click that column to sort. Looks like Adobe and LogMeIn have some work to do on my side ...

You can also do this in System Information. It’s better because it lists all the apps on your system—no need to run them.
 
  • Like
Reactions: lars666 and idunn
Well.... That's what the warnings are for. When you get the warning, the app still works perfectly. The warning is just telling you that that app won't work in some future update, probably 10.14 or maybe 10.15
You can also check Activity Monitor to see if your apps are 32-bit or 64-bit

Note that this is not a default display in Activity Monitor. You have to select "kind" in View/Columns menu to see this information.

I'm not sure I care for this method of warning when they aren't telling you how long you've got before that app has to be replaced. I note for example that the old iWork apps are 32-bit, which means Apple will be warning that their own apps will be obsoleted at some unknown future date. If it's mission critical, you are SOL, even if it's an Apple app. So is the version of FileMakerPro I use and have no other reason to upgrade.
 
This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, . . .

Some people will not upgrade, but this is not a reason to continue to support 32-but apps.

. . . and expose them to security vulnerabilities for no good reason at all.

Actually it does the exact opposite.
[doublepost=1516825537][/doublepost]
Why are they more insecure than 64-bit apps?

Google is your friend:

https://security.stackexchange.com/...-any-security-merits-over-32-bit-applications
 
Note that this is not a default display in Activity Monitor. You have to select "kind" in View/Columns menu to see this information.

It's default in the CPU pane. And as someone else stated, all executables, not just the running ones, can be seen in System Information and it can be detected that way.

I'm not sure I care for this method of warning when they aren't telling you how long you've got before that app has to be replaced. I note for example that the old iWork apps are 32-bit, which means Apple will be warning that their own apps will be obsoleted at some unknown future date. If it's mission critical, you are SOL, even if it's an Apple app. So is the version of FileMakerPro I use and have no other reason to upgrade.

They will tell you before the update that kills support comes out. They did for iOS. They said "In this version we'll show the warnings, in the next major release they die". At WWDC you'll most likely be told.

The current version of iWork is 64-bit. I don't see what Apple can do about old versions of software not being 64-bit. That's what the update is for.
Regarding FileMaker, I see two options - Get FileMaker updated, or don't get macOS updated when the killing blow comes. You can't expect endless support.
And I would like to reiterate that you still have support right now.
 
  • Like
Reactions: martyjmclean
I wonder why Apple has such a fetish for phasing out 32-bit code.

The CPU has NO PROBLEM executing 32-bit code, and there isn't even a performance hit in doing so. There's no real solid reason to discontinue 32-bit support. This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, and expose them to security vulnerabilities for no good reason at all.

MONEY!

All your apps are belong to Apple!

Sincerely,
Tim Cook :D
 
They don't inherently have to be, but if I were to make an argument for their insecurity it'd be this.

Firstly, they can't use as long encryption hashes, and secondly, since the focus is on 64-bit, the dependencies those 32-bit apps may have aren't necessarily as well tested.

For one, NX bit is only available in the 64-bit Page Table.
 
Just look at the cluster that is Windows which still rocks Program Files x86 for legacy purposes.

Having 32-bit apps stop working is significantly more of a negative impact to a user than having two folders for programs.

In any case this doesn't apply because MacOS uses one folder.
 
Note that this is not a default display in Activity Monitor. You have to select "kind" in View/Columns menu to see this information.

I'm not sure I care for this method of warning when they aren't telling you how long you've got before that app has to be replaced. I note for example that the old iWork apps are 32-bit, which means Apple will be warning that their own apps will be obsoleted at some unknown future date. If it's mission critical, you are SOL, even if it's an Apple app. So is the version of FileMakerPro I use and have no other reason to upgrade.

They’ll stop working in 10.15. So, ~September 2019. And of course, you won’t have to upgrade right away.
 
They don't inherently have to be, but if I were to make an argument for their insecurity it'd be this.

Firstly, they can't use as long encryption hashes, and secondly, since the focus is on 64-bit, the dependencies those 32-bit apps may have aren't necessarily as well tested.
It's really just conjecture on your part with no substantiated evidence to support it. In terms of 64-bit hashes, user land apps that are 64-bit have been running on systems since 32-bit Snow Leopard. Another point which I don't think bears scrutiny.
 
Pages 4.3 is my nomination.

If I am right then that's the 09' iWork suite version, right?

Well, I love the old iWork as much as anyone. I still keep them around as well, in conjunction with the new ones. But I very rarely go back to the old iWork, because I'm aware they are EOL. If you save a file in the 09 format, who's to tell it'll even open in any program a few years from now? Sometimes you have to kill your darlings. If you rely on the old iWork for one reason or another, your only solution is to not update macOS. It's that simple. But until the 32-bit killing blow, all is still fine (although even without killing 32-bit apps, you might have noticed parts of the old iWork not working quite as expected. Things change even if it doesn't fully break support)
 
  • Like
Reactions: martyjmclean
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.