Apple prepares macOS users for discontinuation of 32-bit app support
arstechnica.com
arstechnica.com
There were a lot of security exploits that were discovered in old long forgotten 32 bit Code.
Obviously you can work around this for new projects, but it leaves you in the position of needed to keep an old machine or VM around just for opening old project files that would be useless without those plugins. I've talked to multiple people in this situation.
The 64 bit only switch was easy on iOS compared to this. Yes, there's new versions of the applications themselves available, but a whole host of plugins for audio(and i've heard video and photo apps) are going to get left in the dust here leaving people in the lurch.
A computer is a universal machine, and it comes with trade offs. If you want something that doesn’t change, don’t change it.
I have a first-gen Mac Pro (August 2006) and it's 64-bit.
Late-2006 models, including the first-generation Mac Pro, moved from the 32-bit Yonah Core Duo/Core Solo architecture to the 64-bit Conroe Core 2 Duo.
It's not as if there is any real performance penalty of running 32-bit and 64-bit apps concurrently.
It is possible to run older MacOS installs in QEMU under MacOS or Linux on a real Mac.
So if you need 32 bit MacOS apps just run an older MacOS in an emulator.
On Windows they shut out 16 bit apps in 64 bit Windows but DOSBOX and Windows 3.1 under DOSBOX solve that via emulation.
I still have some manuscripts in Pages 09, as Pages 13 never added many of the features. I guess I'll have to look for a new workflow.
Or LibreOffice. Depending on the type of manuscript, Dryad or celtx.
Of course, I don't know your workflow.
If I had to use Word for anything except the most simple documents, I'd probably run it in a VM.
https://arstechnica.com/gadgets/2018/01/office-for-mac-final...
I may simply switch to a markdown template. I used to use Pages for book publishing and copying to html, but the books have become less important.
It was a lucky accident for me that Pages worked for converting my books to html.
- 3 of them are from my (older?) Brother Printer. - 32-bit kdb+ I use sometime for calculations
I can live without them. :)
I'd say serious gamers already switched from macOS to Linux if they don't want to use Windows to begin with. Simply because you can run DX11 games in Wine on Linux, but not on macOS. Borking 32-bit games would only accelerate this shift.
Sincerely, A person who uses MacOS and games on a console.
edit 01: [screenshots]
1) https://screenshots.firefox.com/YJvULhgFlPJKtpD1/www.humbleb...
2) https://screenshots.firefox.com/UMQMitQ4Rm4viSlv/www.humbleb...
edit 02: To play it in a separate tabs as per the scrots just take the key from the purchase page https://www.humblebundle.com/downloads?key=foobarXXXX and apply it to this url like so https://www.humblebundle.com/play/asmjs/ftl_asm/foobarXXXX
As a bonus this allows you to play it on any computer without logging in.
If you want to upgrade your OS, then you need to accept that it will change. This has been the case for all of recorded history.
Keeping macOS (or any OS, really) not updated, is not really an option... unless you're going to keep your computer airgapped.
You might accept to keep unpatched systems, or manage to use them in an airgapped environment. But for a lot of businesses that deploy fleets of Apple hardware, the problem is going to be much more tricky.
(then again, I can see this being an issue only for internally-developed VB6-style apps, which would take a lot of effort to be updated... commercial software like Adobe CS, or even specialist software is going to be upgrade, if not immediately in 1 or 2 major releases, and Apple backports important security patches)
Out of curiosity, I just checked on my Mac and I see a few 32-bit apps. Steam (surprisingly?) is 32-bit only, as are a couple of games. The games I actually play on my Mac have 64-bit slices.