On Twitter, I've shared my distaste for Catalyst apps, as many of them just don't "feel" right to a long-term Mac user. I know that's vague, but today, the vagueness ends, thanks to a deep dive into Apple's recently-released Developer app for macOS. No, the deep dive isn't this blog post you're reading now, but rather one by Martin Pilkington.
He has written a great analysis of the numerous issues with the Developer app. (And importantly, he filed bugs on everything he listed.)
Many of the issues aren't specific to Catalyst, but reflect poor attention to the details that make a Mac app look and act as a Mac app should. Here are but a few of the examples from Martin's analysis:
The focus ring on the search field has square corners • The search field focus ring does not go away if you click elsewhere in the app • Doesn't show window title when toolbar is hidden • Content size is too small • Can't collapse groups in the sidebar • Find toolbar does not share search string across OS
I strongly encourage you to read Martin's article, as it puts into words just why I find many Catalyst apps so annoying to use. In addition, I'm going to provide a couple more examples—using the same Developer app—showing just how non-Mac-like a Catalyst app can be…
Update: The pool is now closed, and the results weren't even close…
Snow Leopard wins in a landslide.
With the 2020 (Virtual) WWDC about a week away—and with it, more than likely, the reveal of Yet Another New macOS Version, I thought it might be interesting to run a little poll…
What is your personal all-time-favorite version of macOS/Mac OS X? Instead of trying to add a polling plug-in here, I quickly created one using surveyplanet. It's set to full anonymous mode, so no IP info is collected—it's just for fun…
Updated and republished for macOS 10.15.5 Supplemental Update 1; skip it unless you really really care about all the macOS releases. Originally published on November 14th, 2005.
Below the break is a table showing all major releases of macOS (previously Mac OS X) from the public beta through the latest public version, which is macOS 10.15.5 Supplemental Update 1, as of June 1st, 2020—the 135th release in total.
Note: Click the ⓘ symbol to read Apple's release notes for a given update.
Shocking even myself, I'm now the owner of a Touch Bar equipped MacBook Pro—I purchased the entry-level 16" model last weekend. Why? I'll save the detailed explanation for an upcoming look at the machine and its performance, but the main goal was to replace two laptops with one.
But just because I now have a Touch Bar-equipped Mac doesn't mean I suddenly like the Touch Bar. In fact, my feelings about it haven't changed since I wrote about it two years ago:
The Touch Bar, despite its name, is actually an Eye Bar: It forces your eyes off the screen, down to the Touch Bar, back up to the screen, repeat ad infinitum.
After some hours working with my new MBP, this is definitely a problem—and it's a problem even when I'm not using the Touch Bar, which is pretty much all the time: I've found that the changing images and colors on the Touch Bar grab my eye every time I switch apps…
The camera was focused on the Touch Bar, but when I'm looking at the screen, I see all that activity just below the screen, and it's really distracting. Thankfully, there's an easy fix, and one I'd not heard of prior to buying this machine…
What follows is a lengthy dive into a semi-recent massive performance improvement in openssl speeds in macOS. As it's long, here's a tl;dr version:
From 10.14.4 to 10.14.5, a change in macOS improved openssl speed benchmark results anywhere from 15x to 30x.
In real world use, encryption of a large sample file (570MB) using a very long password happened nearly twice as quickly as it did before the update.
The version number for openssl (which is really LibreSSL) is the same (2.6.5) in both 10.14.4 and 10.14.5. I also confirmed that the packages, as loaded on the Apple Open Source site, are identical.
The four libraries that openssl links to have the same version numbers in 10.14.4 and 10.14.5.
The binaries for openssl and the four linked libraries all use much less disk space in 10.14.5 than they did in 10.14.4. I can't explain this, except that openssl itself is no longer a universal binary.
I believe the performance boost is due to macOS enabling Intel's AES-NI, which allow hardware acceleration of some key cryptography tasks. But I can't figure out how this change was made, given the above data.
The Apple Open Source site may hold the answers, but that work is beyond my skill level.
Keep reading if you'd like to see how I came to the above summary…
We were fortunate enough to have an Apple ][ in our home, and I remember reading Softline for their game reviews and ads for currently-released games.
It was those ads that caught my eye as I browsed a few issues. Consider Missile Defense, a fun semi-clone of the arcade game Missile Command. To give you a sense of what games were like at the time, here are a few screenshots from the game (All game images in this article are courtesy of MobyGames, who graciously allow use of up to 20 images without prior permission.)
While I have older hardware (a 2013 MacBook Pro) that I use for testing macOS betas—it's now running Catalina—it's often handy to have the latest macOS beta running in VMware Fusion on my iMac. With past OS releases, this has been a relatively easy process. With Catalina, however, attempting the install results in a black screen.
Thankfully, some enterprising Fusion users (Bogdam and intel008) have figured out a workaround. I tried it, and while it did work for me, I had to change the instructions just a bit (read on for the details).
Long-time readers know that I am not a fan of the Touch Bar. I understand that many people like it, but for me, forcing my eyes to the keyboard is not a time saver, especially when the Touch Bar has also taken over the physical Escape key.
If asked, I imagine Apple would say that sales of Touch Bar equipped Macs have been strong, much stronger than their non-Touch Bar alternatives. And I have no doubt that that's true, because Apple has seriously handicapped the non-Touch Bar Macs.
Want a 15" non-Touch Bar MacBook Pro? Sorry, that machine no longer exists—and when it did exist, it was multiple generations older than the Touch Bar models available at the time.
So let's look at the 13" MacBook Pro, where you can still buy a non-Touch Bar model. I configured a non-Touch Bar machine with the fastest CPU available, 16GB of RAM, and a 512GB SSD. I then configured a Touch Bar model to match. Here's how certain features on the two models compare…
In Part 1 of my 2014 vs 2019 iMac comparison articles, I provided an overview and a number of comparison benchmark results. In Part 2, I looked at changes in gaming performance between the two machines.
But there was one more thing I wanted to do: Compare Blu-ray ripping speeds. At the time, though, I didn't have any new movies to rip, and I really didn't want to spend the time re-ripping an existing movie. Now, though, I do have a few new movies to rip, as I'm trying to finish our collection of all the films in the first three phases (now called the Infinity Saga) of the Marvel Cinematic Universe.
That meant buying the films I'd liked the least—The Incredible Hulk and the first two Thor movies. With that came the chance to compare the Blu-ray ripping speed of the two iMacs. I use the method described in my article Revisiting ripping Blu-ray discs, which is this:
Use MakeMKV to create an MKV file on the hard drive that contains the video and audio tracks.
Use Don Melton's Video Transcoding tools to create the final movie from the MKV file.
Using The Incredible Hulk, I timed how long it took to create the MKV file and how long it took to create the finished movie. Without further ado, the results (times are in hh:mm:ss format)…
My new iMac runs Mojave; my old iMac never moved off High Sierra, which I felt was a fine version of macOS. Now that I have no choice but to use Mojave full time (I have it on my laptop for work purposes), I'm finding some annoying changes. Amongst those annoyances, this one is—by far—the most annoying…
That's a set of messages in Mail, as viewed in Classic View mode (using San Francisco Display at 15pt on both Macs).
Somewhere in Apple, someone thought it'd be a great idea to reduce the line spacing in Mail—only when using Classic View, which is my forever-preferred view. Maybe they're doing this to force us to upgrade to the modern view?