A friend recently sent me a link to a large collection of 1980s computing magazines—there’s some great stuff there, well worth browsing. Perusing the list, I noticed Softline, which I remember reading in our home while growing up. (I was in high school in the early 1980s.)
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.)
Stunning graphics, aren’t they?
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?
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.
I knew my new iMac had the wide color gamut (P3) display, but until I used it side-by-side with my old iMac, I didn’t realize just how different things would look. In my comparison test of the two iMacs, there are a couple of photos of onscreen images—one set with the default iMac color profile, the next with the Adobe RGB (1998) color profile—the differences are quite obvious, especially on the default profiles.
Here’s one last image, with a comparison slider, so you can more easily see how the colors change. (Thanks to Kirk McElhearn for the source photo.)
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…
I recently purchased a new 2018 13″ MacBook Air—my first new Mac laptop in over five years. My hope is that this machine can replace two aging laptops: A 2013 13″ Retina MacBook Pro (I use this when I want more “power” or screen resolution) and a 2012 11″ MacBook Air (I use this when I want portability).
Reviews of this machine are all over the net, so I’m not even going to attempt a full review. If you want an in-depth review of the machine, go read Six Colors’ review, or The Verge’s review or Wired’s review…or just start with Macrumors’ round-up of reviews and go from there.
Instead of a full review, I’ll provide some brief thoughts on the machine, then move on to my main focus: The performance changes in Apple’s smallest laptops from 2012 to today, based on comparisons between my three machines. I was interested in how this would turn out, as the two older Macs are both Core i7 CPUs, versus the Core i5 in the new Air. There’s lots out there to read about how the 2018 Air compares to other current machines, or semi-new machines…but I thought it might be interesting to see how performance has changed in five-plus years.
But first, my thoughts on the new Air…
Note: This was originally published in 2015; I’ve updated it with a minor change required for Mojave, and clarified a bit of the text.
macOS includes—and enables by default—translucency, which gives you ‘wonderful’ effects such as this in Calculator:
This is just one example; lots of other apps (Mail and Messages, to name two) contain panes that become grossly distorted by background color bleed-through. I’m not sure who at Apple (Marketing?) thinks this feature is good for productivity , but I find it completely distracting.
As a result, I turn off translucency on every Mac I own. You can do so yourself in System Preferences > Universal Access > Display. Just check the Reduce transparency* box, and you won’t get any more bleed-through. (You’ll also get a solid Dock, and perhaps the world’s ugliest Command-Tab task switcher. Such is the cost of usability.)
* It’s ridiculous that Apple calls this transparency, which is defined as “the condition of being transparent,” and being transparent means being see-through, clear, invisible, etc. This is clearly translucency, or “allowing light, but not detailed images, to pass through.” But I digress…
However, when writing for Many Tricks or Macworld, I often need to take screenshots. And because most users won’t disable translucency, I prefer to take those screenshots with translucency enabled, so that they’re closer to what most users might see. That means a trip through System Preferences to toggle the checkbox, which gets annoying after the second or third time you’ve done it.
There had to be an easier way—and after some missteps, I eventually found it.