Thursday, June 6, 2019

macOS 10.15 Beta


Experience your favorite iPad apps coming soon to Mac. Now developers can easily create Mac apps from the iPad apps you already know and love. They run natively alongside your existing Mac apps so you can drag and drop content between them. And take full advantage of the larger screen and powerful architecture of your Mac to provide a seamless experience across your devices. Enjoy a broad range of Mac apps, with everything from travel, entertainment, and gaming to banking, education, and project management.


With macOS Catalina, there are enhanced security features to better protect macOS against tampering, help ensure that the apps you use are safe, and give you greater control over access to your data. And it’s even easier to find your Mac if it’s lost or stolen.


macOS Catalina includes new features to help everyone get the most out of Mac. Voice Control lets users who don’t use traditional input devices control Mac, iPadOS, and iOS devices entirely with their voice. New tools for users with low vision allow them to zoom a second display or view high-resolution text for items below a cursor.

Here’s the list of new features.

macOS 10.15 Beta Release Notes:

macOS frameworks are now thinned for the x86-64 architecture. Apps that execute i386 code now fail with the EBADARCH error code. The remaining stub frameworks are nonfunctional and exist only for compatibility purposes.

Peter Maurer:

Get off my lawn.

Jerry Jones:

I especially 😳 at the fact that Finder displays “Applications” in a single window, despite it apparently being a collection spread across two separate volumes with different read/write permissions!

Gus Mueller:

Looks like sub-pixel aa is dead dead in 10.15 (it was only mostly dead in 10.14).

Wil van Antwerpen:

This thread describes the problems you bump into if you try to upgrade a macOS Mojave VM to the new beta macOS Catalina. Basically if you run the upgrade then your VM will hang on reboot. If you then try to reboot it in verbose mode, so that you can see what happens, you’ll get the following screen.

Christopher Allen:

A number of people at #wwdc19 today have reported problems using #VMware Fusion to run the macOS Catalina beta (especially as you need it to run #SwiftUI Canvas feature in #Xcode). Reportedly this trick works.


Update (2019-06-10): Marco Arment:

I made a second partition in Disk Utility using APFS space-sharing, installed another copy of Mojave onto it, and upgraded THAT one to Catalina.

Keep FileVault enabled on your main Mojave partition and don’t keep it mounted in Catalina to avoid duplicates in Spotlight.

Update (2019-06-12): Guilherme Rambo:

It looks like NSData.description has changed when linking against iOS13/Catalina, so if you rely on that to generate a string version of your push token, you’re gonna have some issues 😬

It now shows the length and a truncated string of hex bytes, instead of a NeXT-style plist with the entire data’s contents. And it looks like NSDictionary.description calls down do this, so it no longer generates valid ASCII property lists.

Update (2019-06-18): Jonathan Grynspan:

Beginning in macOS 10.15, LSCopyApplicationURLsForURL(), LSCopyAllHandlersForURLScheme(), LSCopyAllRoleHandlersForContentType(), and LSCopyApplicationURLsForBundleIdentifier() all return sorted lists, and it’s documented! 🎉 (NSWorkspace’s equivalent methods do the same.)

12 Comments RSS · Twitter

Ouch... no more sub-pixel antialiasing via the defaults entry? That's the only way I've been able to use Mojave on my non-retina displays without getting a headache.

Is there any technical reason why they'd get rid of the esoteric preference? Seems unnecessarily vindictive toward folks with external monitors (and MacBook Air users, which Apple are still selling non-retina versions of!)

Sören Nils Kuklau

Is there any technical reason why they’d get rid of the esoteric preference?

Yes. Subpixel rendering was never implemented in Core Animation (which is also part of why iOS never got it).

Implementing it in Core Animation would have required doing it straight in the GPU rather than the CPU (since only the GPU knows what you’re alpha-blending against). They never did. Neither did most of the competition; Microsoft has also been phasing out ClearType.

[…] 10.15 Catalina Preview (my post, Catalyst, […]

Thanks for the context! Is there a source for Microsoft phasing out ClearType? I searched around and couldn't find anything to that effect. I have an existing non-retina monitor setup I'd like to keep using if possible, but if everyone's getting rid of sub-pixel antialiasing I guess I'll have to find something high-DPI.

I ended up searching some more and found — via Wikipedia's page on ClearType — that Windows 10 uses ClearType by default for older Win32 apps, but not UWP apps. The reasons for this decision are similar to what Sören mentioned as far as handling animation (in addition to easily-adjustable device orientation changing the sub-pixel layout, and readability concerns on darker backgrounds).

After looking into all this, at least I can understand Apple's and Microsoft's reasoning for their decisions, but at the end of the day it's still an unfortunate situation for folks who still have investments in non-retina monitors. The readability of these devices will get worse over time as sub-pixel antialiasing goes away.

The ideal situation would be support for sub-pixel antialiasing on a per-monitor basis (and have that support be aware of a monitor's physical orientation), but with high-DPI displays becoming more prevalent, it seems like there's no chance for such ideas to get attention.

That’s weird on Windows, because many (most?) new $1,200+ PC laptops still come with regular non-retina displays. It’s not standard like it is with Mac laptops.

Leave a Comment