{"id":26901,"date":"2019-10-15T14:41:15","date_gmt":"2019-10-15T18:41:15","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=26901"},"modified":"2020-04-20T16:57:46","modified_gmt":"2020-04-20T20:57:46","slug":"apps-lost-with-catalina","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/10\/15\/apps-lost-with-catalina\/","title":{"rendered":"Apps Lost With Catalina"},"content":{"rendered":"

Jim Dalrymple<\/a>:<\/p>\n

\n

For those that have been following along, 64-bit is not that new. Apple has been talking to developers about the 64-bit transition for several years. Chances are your apps have already been updated to take advantage of the architecture.<\/p>\n

However, if your apps haven’t been updated, they won’t run on the new operating system. You should be aware of that before you upgrade.<\/p>\n<\/blockquote>\n\n

Peter Cohen<\/a>:<\/p>\n

\n

Important macOS Catalina upgrade tip: Remember that checking your Mac hard drive for 32-bit apps only reveals the apps that won’t work which you have installed<\/em>. It won’t show you anything about the state of apps you have in the cloud, via app stores like the MAS, Steam, etc.<\/p>\n<\/blockquote>\n\n

A. Lee Bennett Jr.<\/a>:<\/p>\n

\n

Not that I’m updating from macOS 10.12 to 10.15 super soon, but I’m looking at the non-64-bit apps and worrying[…]<\/p>\n<\/blockquote>\n\n

TLA Systems<\/a> (previously<\/a>):<\/p>\n

DragThing is written using the 32-bit Carbon APIs that Apple have now removed in macOS 10.15 Catalina. It will no longer run if you update to Catalina, and there are no plans to make a new version that will.<\/p>\n

We are sorry to say, DragThing has launched its last app.<\/p><\/blockquote>\n

John Gruber<\/a>:<\/p>\n

\n

I haven’t used DragThing in many many years, but for a long time it was essential to my workflow, and I firmly believe it was a much better launcher than Apple’s own system Dock ever has been. DragThing had features — like the ability to create custom palettes that only appeared in a certain app — that I don’t know how one would replicate today.<\/p>\n<\/blockquote>\n\n

Fetch Softworks<\/a> (previously<\/a>):<\/p>\n

\n

Apple had made it clear that 32-bit apps like Fetch 5.7 weren’t long for this world, so it looked like the time had come to lay Fetch to rest for good. But I wasn’t quite ready to say goodbye, and it occurred to me that there was a third option, something between finishing Fetch 6 and letting Fetch die: I could port Fetch 5.7’s Carbon user interface to Cocoa and make a 64-bit Fetch 5.8. […] Fetch 5.8 is now in beta testing; you can sign up to test it here. It currently implements about 90% of Fetch 5.7.7’s features with about 50% of Fetch 5.7.7’s reliability.<\/p>\n<\/blockquote>\n\n

AccountEdge<\/a>:<\/p>\n

\n

While AccountEdge is currently a 32 bit application, we have been hard at work on a 64-bit version.<\/p>\n

[…]<\/p>\n

We do not have an update and we still strongly encourage you to delay your upgrade to macOS Catalina until we have released a compatible version of AccountEdge.<\/p><\/blockquote>\n\n

Nilay Patel<\/a>:<\/p>\n

\n

Every late-2000s tech blogger take a moment of silence: the legendary Turbo.264 HD video encoding dongle will never get a 64-bit app and so is now officially dead<\/a><\/p>\n<\/blockquote>\n\n

Fujitsu<\/a> (previously<\/a>):<\/p>\n

\n

The 64 bit application for macOS is not provided for the old scanner models such as ScanSnap S1500, S1500M, and etc. because their support periods have already expired. If you wish to have the 64 bit application for macOS, please consider purchasing ScanSnap products that are currently available on the market.<\/p>\n<\/blockquote>\n\n

Brent Simmons<\/a>:<\/p>\n

\n

It’s not my intention, and it’s not what I want to happen — but NetNewsWire 3.3.2 apparently does not launch in the next version of macOS (10.15, Catalina).<\/p>\n

[…]<\/p>\n

NetNewsWire 3.3.2 was the last release of the full version that I worked on, before selling NetNewsWire to Black Pixel, and I’ve heard from lots of people that they’ve been using it ever since. They never switched.<\/p>\n<\/blockquote>\n

That version is still unequaled, in certain respects.<\/p>\n\n

Stickshift Software<\/a>:<\/p>\n

\n

Mailsmith is no longer under active development. It will not be upgraded for 64-bit macOS compatibility.<\/p>\n<\/blockquote>\n\n

PowerMail<\/a> also looks like it will not get a 64-bit version.<\/p>\n\n

rolleiflex<\/a> (John Siracusa<\/a>):<\/p>\n

\n

I know there is a contingent of people who are stuck at Adobe CS6, whose certain critical components are 32 bit. Since Adobe no longer sells permanent licenses, opting to only rent their software instead, it’s impossible to get these updated. And these expensive and still-in-use licenses are going to die the moment people update to Catalina.<\/p>\n<\/blockquote>\n\n

Toon Boom<\/a> (via Ben Juwono<\/a>):<\/p>\n

If you have Harmony 16 or Storyboard Pro 6 (or prior versions), they will not open in Catalina. Harmony 17 and future versions of Toon Boom’s software will be compatible with macOS Catalina.<\/p><\/blockquote>\n\n

Casey McDermott<\/a> (Hacker News<\/a>):<\/p>\n

Sadly, we just decided to abandon the Cocoa update for our app. It’s not\neasy to walk away from 3 years of work, but better 3 years lost than 5.\nTime will be better spent on our Windows version.<\/p>

TurtleSoft started Mac-only with Excel templates in 1987. The first\nprototype of our current stand-alone accounting app was in the early 90s.\nSince then, programming for Mac has gone through four primary programming\nlanguages (Pascal, C++, Objective C, Swift). Three, soon to be four chip\narchitectures (680x0, PPC, Intel, ARM). Four frameworks (MacApp or Think\nClass Library, PowerPlant, Carbon, Cocoa).<\/p><\/blockquote>\n\n

Casey McDermott<\/a>:<\/p>\n

The plan was to subcontract the Cocoa conversion in parallel. We assumed\nthere would be tons of experienced Carbon->Cocoa programmers so late in the\ngame who could whip it out in a year or less. The bigger offshore subs\nwould only touch it on an hourly basis, estimated $100K to $200K. One QT\nguy quoted $30K for both platforms, which was pretty much our maximum\nbudget. He took the first draw payment then failed. 3 others tried pure\nCocoa for a similar price, but got nowhere.<\/p>

In 2015 we finished the 64-bit prep, and started work on Cocoa in-house.\nBased on past updates, 4 years seemed like plenty of time. Now, after 2 or\n3 programmer-years, a realistic guess is another 2 or 3 needed to finish.\nOur app has a lot of interface code. Running a construction business is\ncomplicated. We do a lot more than QuickBooks.<\/p><\/blockquote>\n\n

Casey McDermott<\/a>:<\/p>\n

Yesterday I checked up on a few other companies we know who have Mac\nsoftware in the AEC market. Most died off years ago. Two are now\nWindows-only. Three will have 64-bit apps “soon”. So far, nobody is ready\nfor Catalina yet.<\/p><\/blockquote>\n\n

TextWrangler<\/a>:<\/p>\n

PSA: with macOS Catalina coming soon, you’re going to need a 64-bit TextWrangler. \n@bbedit\n is it. (Seriously: you’ll feel right at home.)<\/p><\/blockquote>\n\n

Tyshawn Cormier<\/a>:<\/p>\n

What I missed is with 32-bit support gone<\/a>, iPhoto and Aperture no longer launch<\/a>. That’s a little strange. System Information definitely reported both of those apps as 64-bit.<\/p><\/blockquote>\n\n

Howard Oakley<\/a>:<\/p>\n

\n

If you need to retain access to key 32-bit apps, or anything else which won’t run in Catalina, a VM running Mojave or earlier is a highly practical solution, and very straightforward to set up using the latest Parallels Desktop 15.<\/p>\n<\/blockquote>\n\n

My brother has had trouble even getting Aperture to work in a macOS 10.14 virtual machine. See also: Capture One<\/a>.<\/p>\n\n

jessamyn<\/a>:<\/p>\n

\n

Super disappointed in \n@OverDriveLibs\n decision to not create a 64 bit app so Mac users could listen to audiobooks with their existing app. Instead, their whole system silently fails and we have to dig around in help files to figure out wtf is up. <\/p>\n<\/blockquote>\n\n

Joe Fabisevich<\/a>:<\/p>\n

\n

Apple deprecating 32-bit support is completely reasonable but I can’t believe I’m going to have to run a VM to download library books now. Gotta have my library books.<\/p>\n<\/blockquote>\n\n

Kyzrati<\/a> (via Steve Troughton-Smith<\/a>, Hacker News<\/a>):<\/p>\n

Clearly I was already on the fence about the whole Mac thing before, otherwise it might’ve happened earlier (I did spend a while researching and testing the potential for a solution on Macs, in preparation for a potential future public release), but Apple has time and again taken actions which are clearly hostile to developers as they continue the trend of building and reinforcing their own walled garden.<\/p>\n

Among their latest moves, Apple’s newest OS drops support for 32-bit applications, which will unnecessarily render a huge library of software and games unusable on Macs, compared to Microsoft which does a great job of maintaining Windows backwards compatibility in that area even as most modern software tends to be 64-bit. This makes it far easier to hold together Cogmind’s existing tech so I can focus on things players actually care about, like more features.<\/p><\/blockquote>\n\n

Aspyr<\/a> (Hacker News<\/a>):<\/p>\n

\n

Any 32-bit Aspyr games not listed above will be incompatible with MacOS 10.15.<\/p>\n<\/blockquote>\n\n

jasper<\/a>:<\/p>\n

\n

in a few days with the launch of the new 64 bit-only mac os, millions of games will no longer work, including my own. how are are other developers approaching this? will you remove your 32 bit games from Steam etc?<\/p>\n<\/blockquote>\n\n

The Tape Drive<\/a> (via Hacker News<\/a>):<\/p>\n

A bundle called IncompatibleAppsList.bundle found in \/Library\/Apple\/Library\/Bundles\/<\/code> in macOS Catalina contains [a list<\/a>] of 235 apps that are incompatible with Catalina. This list is used by the Catalina installation process to show the user a list of currently installed apps that are incompatible. Many of the apps listed are included only because older versions of the apps are incompatible as noted by the strings included with the bundle.<\/p><\/blockquote>\n\n

Previously:<\/p>\n