Back in 2015, I created a set of 5120×2880 deep space desktop images for my then-newish Retina iMac, using images from the Hubble space telescope.
Recently, the Hubble team released the absolutely mind-bogglingly-massive Hubble Legacy Field image…
The snapshot, a combination of nearly 7,500 separate Hubble exposures, represents 16 years’ worth of observations. The ambitious endeavor is called the Hubble Legacy Field. The new view contains about 30 times as many galaxies as in the HUDF. The wavelength range stretches from ultraviolet to near-infrared light, capturing all the features of galaxy assembly over time.
The image mosaic presents a wide portrait of the distant universe and contains roughly 265,000 galaxies. They stretch back through 13.3 billion years of time to just 500 million years after the universe’s birth in the big bang.
Despite those staggering figures, this image still represents only a tiny portion of the sky, covering roughly the area taken up by the Moon in the night sky.
I downloaded the 700MB 25,500×25,500 PNG version of the image, and set to work making some new 5120×2880 desktop images. You can read more about the process in an upcoming post, but for now, here are the resulting images…
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)…
Shortly after I bought my 2014 iMac, my third-party mouse died. So I started using the Magic Mouse that came with the iMac, and added “get new third-party mouse” to my to do list. Although I never found the Magic Mouse all that comfortable, I kept putting off replacing it.
Finally, when I ordered the new iMac—yes, that task sat on my to do list for nearly five years—I decided to go back to an ergonomic button-laden third-party mouse. After some searching and hand-fit tests, I bought a Logitech MX Master 2S ($70 at Amazon) mouse1Note that this is definitely a right-hand-only mouse, and Logitech doesn’t appear to offer a left-handed version. Sorry, lefties..
Note: I really dislike reviews that are so short they read more like press releases (and sometimes actually are reprinted press releases). I don’t do a ton of reviews here, but when I do, they tend to be long, because I like to use a product first, then review it in depth.
So what follows are many words (and images) about a computer mouse. If you’d like the tl;dr version instead, here it is: I love the MX Master 2S due to its great ergonomics, customizability, and easy multi-computer support. Keep reading for the much longer version.
If you weren’t reading along this week, I spent the last four days—parts one, two, three, and four—talking about my Tesla Model S and how much I love it.
Today’s surprise ending is this: I sold the car. What I’d replace it with? This…
Obviously that’s another Tesla Model S—a used Model S. It is, in fact, a 2016 Models S 90D—yes, basically the exact car I had, but not really—more on that in a bit. My wife and I call it the unicorn car; read on to understand why, and why I made this trade. (As I was writing this, I learned that others had already used that phrase for this particular vintage of the Model S.)
This is Part Four of a four-part series on our 2016 Tesla Model S. In Part One, I covered why we chose the Model S, the cost of the car, and a bit about Tesla the company. In Part Two, I listed some of the things I love about the car. In Part Three, I listed more of the things I love, plus those things I hate. In today’s Part Four, I’ll discuss what it’s like living with an electric car, cover a somewhat long road trip I took last fall, and offer a few thoughts on the future of auto electrification. Finally, tomorrow’s Part Five will provide an unexpected ending (of sorts) to the series.
Living with an electric car
My two-plus years with an electric car have been basically a non-event. There are many reasons for this, including the fact that I work at home, and that we have non-electric vehicles, so the Tesla doesn’t have to do everything. (But even if I commuted, with the car’s range of 280 miles, I think it’d still be a non-event.)
This is Part Three of a five-part series on our Tesla Model S. In Part One, I covered why we chose the Model S, the cost of the car, and a bit about Tesla the company. In Part Two, I listed some of the things I love about the car; today’s Part Three has more of the loves, as well as the not-so-loves. Part Four will discuss what it’s like living with an electric car, and my thoughts on the future of auto electrification. Finally, Part Five will provide an unexpected ending (of sorts) to the series.
Continuing with the things I love about the car and its infrastructure, and then getting to the not-so-loved things…
This is Part Two of a five-part series on our Tesla Model S. In Part One, I covered why we chose the Model S, the cost of the car, and a bit about Tesla the company. In today’s Part Two, I’ll discuss some of the things I love about the car; Part Three will have more of the loves, as well as the not-so-loves. Part Four will discuss what it’s like living with an electric car, and my thoughts on the future of auto electrification. Finally, Part Five will provide an unexpected ending (of sorts) to the series.
What I love about the car
Everything. OK, that’s not true. But there is a huge list of stuff that—even after nearly three years—helps make any drive in the Tesla an enjoyable experience. The list is generally ranked by order of importance to me, though a lot of these would be ties if I had to absolutely rank them. Most of these things are particular to Tesla’s cars (and some to the Model S in particular), though a couple are generally true of any electric vehicle.
Coming up on three years ago, in June of 2016, I replaced my Subaru Legacy with an electric car. Not just any electric car, but a Tesla. Our Tesla is a 2016 “original nose” Model S 90D, which roughly translates to “a very expensive, quite large four-door sedan with about 290 miles of range, all-wheel drive, propelled by a couple of powerful electric motors.” This is not only the most expensive car—by far—we’ve ever owned, but (spoiler alert) it’s the best car we’ve ever owned.
I’ve been writing this post—off and on—almost since the day we bought the car. So why has it taken so long to publish?
Earlier today, I noticed that the robservatory database was massive—over 1GB in size, which it shouldn’t be anywhere near (it’s usually around 100MB). This is over the database size limit at my host, so I couldn’t add any new content (nor could visitors comment, create accounts, etc.)
My host offers phpmyadmin acccess, so I connected to the database to try to figure out what was going on. Using phpmyadmin, you can browse tables, perform SQL commands, and export and import data—it’s a must-have tool for managing remote databases.
The first challenge was to figure out which table was causing the problem. To help with that, I wanted to see which WordPress tables were the largest, as that should be a good hint. A web search found lots of possible solutions, but I liked this one the best. Within that thread, I slightly modified one of the queries to do what I wanted:
table_name AS "Table",
ROUND(((data_length + index_length) / 1024 / 1024), 2) AS "Size (MB)"
WHERE table_schema = 'YOUR_DATABASE_NAME_HERE'
ORDER BY (data_length + index_length) DESC;
I’ve been updating my A useless analysis of macOS (OS X) release dates post for nearly 13 years now (OMG). Over the years, the one thing that’s bugged me was that I couldn’t find a good way to have fixed column headings on that post’s incredibly long scrolling table.
Hooray for fixed headers! Read on if you’d like to use this trick yourself…