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…
I received an email from a user this morning, asking if Name Mangler was compatible with Catalina, as he'd seen a report telling him it was 32-bit. This was an odd thing to read, because Name Mangler 3 has been 64-bit from the beginning, way back in 2013.
I asked what report he was looking at, and he told me it was from the Legacy Software tab in System Information. I decided to see what the report had to say about my machine, so I launched the app (Option-click the Apple icon in the menu bar), went to the Legacy Software tab, and saw this…
May 26 2020 Update: The 2020-003 Security Update for Mojave will reset the red flag (and deprecate the command used to ignore the update). However, these steps do still work, so you just have to repeat Miles' solution again. And after you do, do not open the Software Update panel, or the red badge will return. (But if it does, just run the commands yet again.)
May 9 2020 Update: Commenter Miles Wolbe has come up with a much better solution. Ignore everything in this tip, and just run this Terminal command:
If you're interested in why this works, Miles explains it in more detail. I've tested this method, and it works—no more agent required!
I have no plans to move my main iMac to macOS Catalina, at least for the forseeable future. There are two key apps I use—Fujitsu's ScanSnap scanner software and the Many Tricks' accounting app—that are both 32-bit. In addition, there are changes in Catalina relative to permissions that make it somewhat Vista like and slow down my interaction with the system. (My MacBook Air is my "production" Catalina Mac, and I have an older retina MacBook Pro that I use for Catalina betas.)
But Apple really wants people to update to Catalina, so they let you know about Catalina…constantly, it seems. In System Preferences > Software Update, you'll see this…
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).
Updated for the fifth release of macOS Mojave (10.14), which came out on January 22, 2019
When the third release of macOS High Sierra came out, I charted the pace of its updates compared to all prior Mac OS X/macOS releases. I said I planned to keep that chart current, but decided that I'd use the fifth release (typically around six months from the OS release date) as the baseline.
Here's the latest update for Mojave's fifth update—a bit late, as that update (10.14.3) came out back in January. (Note that 10.0 is not shown, as it had only four releases.)
macOS 10.13 is clearly the outlier of the bunch, taking just 120 days to reach its fifth update, but macOS 10.14 is the only other release to hit its fifth update in under 200 days.
It certainly appears that Apple started pushing more updates more quickly when macOS 10.13 was released, but it's hard to say just why: Is it a new strategy to push updates more quickly, is it buggier macOS releases, or are they catching bugs due to better reporting, the public betas, etc.? I don't have a clue, but it's clear that "more and faster" is a good summary of the last two macOS versions' update releases.
I recently reviewed my new third-party mouse, the Logitech MX Master 2s ($70 at Amazon). I love all the customizable buttons on this mouse, and in particular, the ability to create gestures (which are simply a directional drag while holding down a button).
I've used two buttons to create a total of 10 gesture actions on my mouse:
I created the above image from the Logitech Options app, so I can refer to it if I forget which action I've assigned to which gesture. But it's a pain to find the folder on the disk and open it just to see the image. Then I remembered I had an unused button on my mouse1The upper button of the two near the side scroll wheel…
Note: While the following is specific to my Logitech mouse in terms of implementation, read on if you're curious about how to access QuickLook previews from Terminal and/or via a simple AppleScript.
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?
Update: After I posted this, Brad Oliver contacted me on Twitter about the frame rates for DiRT Rally—he commented that the fact that they were clustered around 60fps made him think I'd left vertical sync (Vsync) on…and he was right. I've updated that section with the modified results, as well as one additional comparison I forgot to include the first time.
Oh, and in case you don't know Brad…he was directly involved in porting DiRT Rally to the Mac for Feral, so he knows his stuff! Thanks Brad!
In part one of the comparison between my old and new iMacs, I provided a brief overview of the new machine, tech specs for both, and a number of benchmarks. (I also tested the video card against a Windows GeForce GTX 1080, and posted a slide-over image that demonstrates the wider color gamut on the new Mac.)
In today's second (and final) part, I'll take a look at video processing performance (via iMovie), how well the new iMac handles gaming, and then wrap up the whole series.
My 2019 iMac has the new AMD Pro Vega 48 video card, the fastest video card Apple has offered in a (non-Pro) iMac. But just how fast is it? I'll have more to say about it in an upcoming "games shootout" with my 2014 iMac, but I was also curious as to how (badly) it might compare to the video card—an NVIDIA GeForce GTX 1080—in my 2017 Frankenmac.
While I'd love to be able to compare the performance under macOS on Frankenmac, that's not possible as I uninstalled it a while back—I'd been unable to update to Mojave due to a lack of NVIDIA drivers for Mojave. (Which is related to all of this, in that you cannot use an NVIDIA card—with acceleration—in Mojave, even in an external GPU box, because it seems Apple and NVIDIA aren't on speaking terms right now.)
However, because a number of the benchmark apps I used in my 2019 iMac vs 2014 iMac—Part One comparison test also run on Windows, I was able to do some head-to-head testing, even if the difference in the OS adds a layer of unknown to the results.
Going in, I was pretty sure I knew what the results would show: The Windows PC was going to crush the iMac in anything graphically related, but lose in the CPU tests. While the AMD card is a big step up from previous-generation iMacs, it's nowhere near bleeding edge—it's more like "minor scrape" edge—in the Windows world.
Anyway, I ran a bunch of tests, and the results were pretty much as I expected…