The Robservatory

Robservations on everything…

 

Apple

A useless analysis of macOS (OS X) release dates

Updated and republished for macOS 10.13.5; 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.13.5, as of June 1st, 2018—the 112th release in total.

Note: Click the ⓘ symbol to read Apple’s release notes for a given update.

(more…)

A look at seven years of my Mac App Store activity

The other day while browsing the Mac App Store, I clicked on an app’s web site link, only to be greeted with this lovely “Can’t Find the Server” error message in Safari…

That got me wondering about just how often that happens—how many apps are out there that are still in the store, yet their developers have closed down their work and moved on to other projects? I thought it might be interesting to look at my App Store purchases and see just how many of them had broken web site links in their App Store entries.

Then I thought that as long as I was looking at each of my purchases, I might as well collect some additional data. So I put together a simple FileMaker Pro database with a few fields for each app…

During my spare time over a few days and nights, I went through every entry in my App Store Purchased list (after unhiding some apps that I’d hidden). I installed them (if they weren’t already installed), tried to run them, and completed the above data card for each app.

I then tried to answer some questions about my App Store purchases over the years…

  • How many apps have I purchased? [116]
  • How many do I still use? [35]
  • What types of apps do I purchase? [A variety; lots of games]
  • How many appear to have no-longer-there developers? [5]
  • How many of the apps are still in the App Store? [90]
  • How recently have those apps been updated? [Check the chart]

If you want more detail than the [bracketed tl;dr notes] provide, keep reading…

(more…)

6,399 reasons why I haven’t yet replaced my iMac

My main machine is a late 2014 27″ iMac with a 4GHz Core i7 CPU, 24GB of RAM, and a 256GB SSD (plus a big external RAID for most of my files). While it runs fine, I would like something with Thunderbolt 3 support, with faster graphics for X-Plane, and with more computing power for ripping Blu-Ray discs. It’s also beyond AppleCare age, and if something fails, it will be expensive and time consuming to repair.

When the iMac Pro came out, I was intrigued, but the price point is scary high and there was the “new new” Mac Pro on the horizon—potentially a cheaper alternative, given the display wouldn’t have to be bundled (and upgradeability is a good thing). I was hoping for an update on that machine at WWDC this June. Instead, we got the update much earlier, though it’s not was I was hoping to hear: The new new Mac Pro won’t be released in 2018.

As a result, if I want to replace my iMac this year, I have only two choices: A new iMac non-pro, or a new iMac Pro. (In theory, I could look at a MacBook Pro with an eGPU for graphics, but I despise the Touch Bar, and that’s the only way to get the highest-spec MacBook Pro. But I really want a desktop Mac, not a laptop-as-desktop Mac.)

So just what would I be getting for my money with either machine? And how do those machines compare with the Frankenmac homebuilt I put together last year? And perhaps more intriguingly, how do they compare with the 2013 “new” Mac Pro that Apple still sells today?

To answer those questions, I turned to the Geekbench 4 benchmark app, which includes both CPU and graphics (they call it Compute) benchmark tools.

(more…)

How to rename dropped pins in macOS Maps

Today I wanted to do something that seemed simple: Add a pin to Apple’s Maps app on macOS High Sierra, then rename the pin.

But after trying everything obvious, I was stumped, and took to both Twitter and web searching. About the same time I found the answer on the web, I also received a tweet from @tmneff with the same answer.

This seems absolutely crazy, but here’s how you name a dropped pin in Maps on macOS—these are just the instructions from the linked web page, with a few added screenshots:

  1. Drop the pin.

  2. When the info box appears, click the small circled ‘i’ at the right.

  3. In the new window that appears, click the heart (Favorite) icon, to make your new pin a favorite.

  4. Click in the search bar, then highlight the Favorites entry and click it.

  5. When the list of favorites appears, you’ll see an Edit box at the lower right corner; click that, and you can then click-and-edit any of the pin names as you would a filename in Finder.

    You can also delete favorites here by clicking the ‘x’ icon.

  6. Click Done, and your custom name should be saved with the dropped pin.

Apparently in iOS, you’re prompted for a name when you tap the Favorite icon—that makes a lot sense, and macOS should follow the same convention. But it doesn’t, sigh.

Number of days until fifth update for macOS releases

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, so here it is now that the fifth High Sierra update (10.13.3) is out. (Note that 10.0 has vanished from the chart, because it had only four releases.)

Click the above image for an in-window larger version, or just view the full-size version directly.

As you can see, macOS 10.13 took just 120 days to reach its fifth update; that’s nearly half the time (229 days, macOS 10.11) as the next quickest release.

Is it better software updating, catching more bugs earlier and pushing releases faster, or is it just buggier software receiving multiple quick-release critical updates? I obviously don’t know, but my perception as a user is that it’s the latter.

The iMac Pro—and upcoming Mac Pro—are Apple’s ‘halo cars’

Writing on his blog, Kirk McElhearn talks about profit and the iMac Pro/new Mac Pro (emphasis added):

I’m speculating, but I think Apple won’t be making much of a profit from the iMac Pro, or the coming Mac Pro, but rather needs to have these computers as flagship devices to show that the company can innovate. If they take a loss, because of R&D costs, it’s not a big deal, because for every iMac Pro or Mac Pro they’ll sell, they probably book 10,000 iPhones.

I think Kirk’s spot on here (though this being Apple, I wouldn’t be surprised if they make a small profit on the Pro models). And there’s a perfect corollary in the automotive world: halo cars

A halo vehicle (or halo model) in automobile marketing is one designed and marketed to showcase the talents and resources of the manufacturers and to promote sales of other vehicles within a marque.

Consider Ford and the new Ford GT, which is a stunning $495,000 sports car…

Ford won’t sell may of these—I believe they’ve capped production at 1,000 units or so, and they’re probably taking a loss on each car. But it’s a car that shows what Ford can do given unlimited budget and working outside the constraints of a typical production line—it takes one full day to assemble each car. Compare that to the roughly 300,000 Ford Fusions sold each year, which means they’re producing over 820 cars per day.

It also gives the owner of a Fusion or Fiesta or Mustang the ability to say “Yea, it’s a Ford—the same company that makes that amazing GT.” It may even draw them into a showroom to see the car, where they may leave with some lesser vehicle. (Though with so few GTs being built, Chevrolet’s Corvette is a better real-world example of a halo car, as you can find those at any Chevy dealer.)

Thinking about the iMac Pro/new Mac Pro as Apple’s halo cars makes perfect sense. These are expensive machines that will sell to relatively few people, but every Mac (and iPhone) owner can say “Yea, the same company that makes those amazing high-end desktop machines.” It may also draw users to an Apple Store to see this amazing metal, and they may end up leaving with a “normal” iMac or MacBook Pro.

And it lets Phil keep saying “Can’t innovate any more, my ass!” for a few more years.

macOS quality as measured by update release rate

There’s a lot of chatter out there that High Sierra is potentially the worst macOS release ever, in terms of bugs and broken or missing functionality. From the recent Month 13 is out of bounds log spewage problem to the root no password required issue (whoops!) to a variety of other glitches, High Sierra has presented many users, myself included, with a near-constant stream of issues.

But is it actually any worse than prior macOS/OS X1I’ll just call it macOS from here on. releases? There’s really not a lot of information to go on, given Apple’s very-private development process and non-public bug tracker.

However, the one data source I do have is a list of every macOS release date. With 10.13.2 having just been released, I thought it might be interesting to see how quickly the third update arrived on each version of macOS. If High Sierra is worse than usual, I’d expect that the time required to reach its third update would be notably less than that of other releases.

After some fiddling in Excel, the data proved—with some caveats and observations—my hypothesis…

(more…)

Month 13 is out of bounds

And obviously, it would be, because there is no month 13. But if you’re unlucky enough to be a Mac user in the month of December, 2017, then you’ll probably be seeing a lot of “Month 13 is out of bounds” messages in your Console. And by ‘a lot,’ I mean an exceedingly excessive never-ending stream of spewage…

Thousands and thousands and thousands of them—I’m getting anywhere from two to 20 per second, continuously. Ugh.

This just started happening this morning, and it’s happening on all my Macs. I found one Apple developer forum thread that talks about the problem, and user Helge seems to point to a bug in mdworker

(more…)

The fundamental problem with the Touch Bar

Today, via a link posted on Six Colors, I read Steven Acquino’s The Touch Bar Makes the Mac More Accessible to Me, in which Steven shares his positive experiences with the Touch Bar:

Where it shines considerably is as an alternative to keyboard shortcuts and the system emoji picker. Tapping a button on the Touch Bar is far more accessible than trying to contort my hands to execute a keyboard shortcut or straining my eyes searching for an emoji.

Usability is definitely an individual thing, and Steven makes a good case for why he likes the Touch Bar. However, Steven doesn’t mention a fundamental issue with the Touch Bar. Nor does Marco Arment in his Fixing the MacBook Pro article. To me, this unstated issue is the main problem with the Touch Bar, and it’s one that Apple can’t fix with new features or tweaks:

You cannot use the Touch Bar without looking at it

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. There’s nothing physical about interacting with the Touch Bar, aside from using your finger: There are no defined button areas, and there’s no haptic feedback when you tap something. So you absolutely must look at the Touch Bar to interact with it.

When the new MacBooks were released, I spent about 30 minutes testing a Touch Bar-equipped version in an Apple Store, and this constant moving of my eyes’ focus from keyboard to screen to keyboard to screen to…well, you get the idea…was incredibly disruptive. To use the Touch Bar, I’d have to change my focus to the keyboard, then refocus on the screen, taking time to find my active window and locate the mouse cursor. This did not make for a pleasant user experience.

As but one example, Steven mentions using the Touch Bar for zooming:

In addition, the Zoom feature—one of the Touch Bar’s many accessibility features—makes seeing controls much easier.

Granted, there are some extra capabilities in the Touch Bar zoom, but using the Touch Bar for zoom seems infinitely harder—and more disruptive—than my preferred approach:

You can really customize zoom in that panel, including making it usable via the keyboard, setting zoom limits, and more. I keep it simple, though, with a mouse-assisted full screen zoom.

To zoom my screen, I hold down the Control key, then scroll my Magic Mouse with one finger, and I get infinite and easily-controllable zoom, all without ever taking my eyes off the screen. To zoom with the Touch Bar, I’d need to look at the Touch Bar while I tapped on it to get into zoom mode, then look back to the screen as I zoomed. That seems much tougher, and again, my eyes have to go from screen to keyboard and back—and do so again when I’m done zooming to exit zoom.

Using a Mac should be about doing things efficiently, and to me, the Touch Bar is an incredibly inefficient solution to a non-existent problem. I’m with Marco, and hope that future laptops either remove the Touch Bar completely or make it optional.

The iPhone 8 Plus’ glass is not all it’s cracked up to be

This morning, I was thinking about putting a clear screen protector on the iPhone 8 Plus, just because I had one that came with one of the cases I purchased. While cleaning the glass, though, I noticed something disconcerting: My iPhone 8 Plus is already showing fine scratches on the glass.

Compare my year-old iPhone 7 (top) with the weeks-old iPhone 8 Plus (bottom)…

Both phones are in similar cases that extend above the edge of the glass—I tried two minimal cases on the iPhone 8 Plus, but have only used the full-sized cases out in the “real world.” Both phones have been used in similar ways, sitting in my pants pocket or in a tray in my car. After a year of such treatment, the iPhone 7 glass looks practically brand new. The iPhone 8 Plus glass, however, is already showing fine scratches. (There are similar scratches near the bottom of the phone, too.)

These scratches aren’t—yet?—visible in day-to-day use, but it concerns me that they’ve developed to this degree after only a couple weeks’ use. How bad will things get after a few months?

Are any other iPhone 8 (Plus or non-plus) users seeing such scratches on their displays? I’m tempted to go visit the Apple Store with my phone, because I can’t believe this is normal, especially given how well the iPhone 7 (and all my prior phones) have resisted scratching.

The Robservatory © 2018 • Privacy Policy Built from the Frontier theme