Is it also fixing security bugs or does it fixe some general macOS bugs related to Spotlight and Finder?
On the Mac side it is easier to deal with this 32-bit rapture than on the iOS side.
FCP 7 is keeping me on Sierra for now.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.
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.Kind of a bummer. My 2009 macbook pro only has 4gb of ram (2nd slot is broken). So I would effectively be down to 2gb..
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.
FCP 7 is keeping me on Sierra for now.
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.
Surprised the GPU hasn't given up on life yet.
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 ...
Crappy. I have scores of vintage apps that have no modern equivalents that I use regularly that will be nuked.
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
Twice under warranty.
Like what ones?
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.
Why are they more insecure than 64-bit apps?
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.
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.
Crappy. I have scores of vintage apps that have no modern equivalents that I use regularly that will be nuked.
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.
Just look at the cluster that is Windows which still rocks Program Files x86 for legacy purposes.
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.
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.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.
Pages 4.3 is my nomination.