Oh, so it's ok to drop $650->$1,000 on the device but damn the guy, who wrote the App, and asked you for $1?
JFC...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple to Phase Out 32-Bit Mac Apps Starting in January 2018
- Thread starter MacRumors
- Start date
- Sort by reaction score
Oh, so it's ok to drop $650->$1,000 on the device but damn the guy, who wrote the App, and asked you for $1?
JFC...
Given that people have to opt-in for Apple to collect the information to build the pie charts - I doubt it. Yes, they know how who bought what 32 bit apps from the App store, but they don't know how many old apps people are running.
I'm happy to buy an app, but not rebuy it for the sake of it. I don't have money to throw around like that. Many of the programs I have on my Mac are in excess of $100.
Yes that's exactly my point. Apple has long history of this thing
No, that's the point, they don't have a long history of this sort of thing.
There are programs written in 1984 that would still run on a Mac running a current OS in 2006. No, not all of them, but some of them absolutely would. Programs written in the early to mid '90s weren't even likely to be a problem then.
Now? They've broken everything in the mid '90s, everything in the early '00s, and they're now talking about breaking things written as late as a few years ago.
I didn't think there even was such a thing as 32bit apps anymore. We've had 64bit OS and software for quite some time now.
A 99 cent app, sure. A $200 Office Suite? Not so much. $100 Graphic editor? Again, different expectations. (Talking Mac software).
Quick by an iPhone 5 or 4S and load iCloud and restore your apps while you can!!
[doublepost=1496809083][/doublepost]
Are you referring to the "Do as your told, OS" button as the "OK" only selectable button? Hmm never thought of it like that. How many are presented in OSX in the millions of options vs say Win7/8/10? Hmm.
A few things:
a) DVD Player (Apple-provided in macOS) is 32-bit. Hopefully they won't forget to update it to 64-bit.
b) Will this lock down apps ONLY from the App Store, or individual apps downloaded from the Internet? If only from the App Store, I can see this having little impact for the time being. If it's all 32-bit apps, regardless of location downloaded, we may have a WW3 on our hands. Exaggerating slightly, but yeah, it won't be pretty.
c) I'd create a macOS Sierra or High Sierra partition/cloned external HD with all essential 32-bit apps to run if necessary. May not be the most convenient solution, but better than nothing.
a) DVD Player (Apple-provided in macOS) is 32-bit. Hopefully they won't forget to update it to 64-bit.
b) Will this lock down apps ONLY from the App Store, or individual apps downloaded from the Internet? If only from the App Store, I can see this having little impact for the time being. If it's all 32-bit apps, regardless of location downloaded, we may have a WW3 on our hands. Exaggerating slightly, but yeah, it won't be pretty.
c) I'd create a macOS Sierra or High Sierra partition/cloned external HD with all essential 32-bit apps to run if necessary. May not be the most convenient solution, but better than nothing.
As a note, it's legal to virtualize Mac OS X on Apple hardware, so you can run Sierra inside of VMWare or Virtualbox.
Your reasoning is flawed. Unless you're proposing to drop 64 bit support, you must have 64 bit. The question is then whether to support 64/32 or only 64. Supporting 64/32 is always going to cost more OS storage and hence update bandwidth. There's no argument.
Check it out yourself: https://www.catalog.update.microsoft.com/Search.aspx?q=KB3213986
I was underestimating, the difference is now half a gig more for 64/32.
The moment you load a 32 bit program, all the 32 bit libraries have to be loaded and that far outweighs the additional pointer load a 64-bit implementation takes. For the simplest GUI programs in OS X, it's around 100-150 MB of shared stuff, which by my calculation is 37.5 million pointers. That's a lot in the scheme of things.
The other point is that both AArch64 and AMD64 made architectural cleanups over their 32 bit versions. If you can eliminate the need for 32 bit compatibility in hardware, you can gain in power and speed.
Last edited:
Just don't update beyond High Sierra. Alternatively you can run an older OS in a VM or dual boot. I think there are still plenty of options.
Hopefully someone will write a sort of shell that will let old apps work. Burn has been one of my best tools for creating and copying CDs - especially audio CDs since Disk Utility won’t. And it lets you copy from one to CD directly to another if you have two drives.
But it was written for OS X 10.6, hasn’t been updated since
I guess I’m correct in that we won’t be able to run non-Mac AppStore apps either?
But it was written for OS X 10.6, hasn’t been updated since
I guess I’m correct in that we won’t be able to run non-Mac AppStore apps either?
I use Photoshop CS6 from time to time. If I were a creative pro, I'd happily pay for CC if it weren't so annoying itself. They try to bundle some cloud sync software in that is really just malware as far as I'm concerned.
You're mad because people want to stay in their ecosystem/workflow? Maybe you should find more sensical things to be mad about.
A little hack isn't going to fix this. They're removing the 32-bit libraries, so you're out of luck unless you've got a VM ready.Hopefully someone will write a sort of shell that will let old apps work. Burn has been one of my best tools for creating and copying CDs - especially audio CDs since Disk Utility won’t. And it lets you copy from one to CD directly to another if you have two drives.
But it was written for OS X 10.6, hasn’t been updated since
I guess I’m correct in that we won’t be able to run non-Mac AppStore apps either?
Ok i think this is bundled with some specific hardware. I'd suggest to either dual boot or keep a 32bit capable OS on a bootable external drive. Of course you can also just keep on using High Sierra (and nothing afterwards). You'd have to check if it's working when running in a VM (as it is bundled with a special hardware). Just wondering if iMovie (or fcp) isn't up for the job too if it's using a standard video capture API.
Have you tried capturing the footage through QuickTime X? If not, try this:
Open QuickTime Player.
Select File>New Movie Recording.
The resulting window will probably display your iSight camera. Click the down arrow to the right of the record button, and you should be able to select the source(s), quality, and destination of the captured file.
I wouldn't capture directly into h264 by the way - but use ProRes as an intermediary format and later compress to h264 (after cutting, color correction, deinterlace, etc.)
Last edited:
You're saying that iOS updates are quick and easy? You're saying your Apple product has more than enough RAM?
Why? ARM runs 32-bit software fine. iOS was 32-bit until recently. ARM also sucks in a PC, AND it's incompatible with everything of course, so they won't do it anyway unless something changes.