apple

I had to pause some of my work getting a current-gen AMD graphics card running on the Pi 5 and testing a 192-core AmpereOne server to quickly post on the M4's efficiency.

I expected M4 to be better than M1/M2 (I haven't personally tested M3), and I hoped it would at least match the previous total-system-power efficiency king, a tiny arm SBC with an RK3588 SoC... but I didn't expect it to jump forward 32%. Efficiency gains on the Arm systems I test typically look like 2-5% year over year.

The M4 mini I just bought reaches 6.74 Gflops/W on the HPL benchmark.

UPDATE 2024-11-20: I re-ran all my tests without my 10 Gbps Ethernet plugged in, and the efficiency is even better. I also re-tested LLM performance, and made this quick video:

Many years ago, I decided to migrate my photo library from Apple's now-defunct Aperture to Photos, so I could take advantage of Apple's iCloud Photo Library (don't worry, I still have three full complete local backups, plus a separate cloud backup besides Apple's iCloud originals).

One pain point is RAW support. As camera manufacturers add new models, their proprietary RAW codecs are updated, and software vendors like Apple, Adobe, and Microsoft have to update photo editing tools to work with the new camera models.

I don't envy them this task, but as Photos was Apple's official successor to Aperture (a pale shadow to be sure, but it has its merits as a semi-decent library organizer), they've generally done well supporting new camera models. The compatibility list for macOS Sonoma, iPadOS 17, and iOS 17 is a testament to that effort.

This blog post will serve as my long-term build log for the Power Mac G4 MDD I started restoring in the video Retro Computing Enthusiasts are Masochists in early 2024. See also: Build log: Macintosh PowerBook 3400c.

The G4's swan song

Apple's Blue-and-White G3 brought a bit of fun into the industrial design of Apple's pro desktop line of Macs. The four-handle polycarbonate design language progressed through a few generations of G3 and G4, culminating in the 'Mirrored Drive Door' model.

This model is also nicknamed 'Windtunnel' for the amount of noise it generates. The original G3 minitower ran a single 300 MHz G3.

The MDD came in configurations with up to two 1.42 GHz G4 (PowerPC 7455) CPUs, two full-size optical drive bays, and even more expansion.

This blog post will serve as my long-term build log for the Macintosh PowerBook 3400c I started restoring in the video Retro Computing Enthusiasts are Masochists in early 2024. See also: Build log: Power Mac G4 MDD.

The fastest laptop period

It's 1997. Apple just re-acquired Steve Jobs, but he hasn't been around long enough to materially impact the next few months of product launches.

Gil Amelio, seeing a gap in Apple's laptop offerings, decides to throw the kitchen sink at the market, in the form of the PowerBook 3400c. It works.

This laptop was the platform for the first G3 laptop, the short-lived 'Kanga', which used almost an identical design as a stopgap for Apple to later introduce the iconic Wallstreet G3.

In spite of Microsoft's cryptic announcement of Project Volterra, and Qualcomm's continuous lineup of 'flagship' ARM SoCs for Windows, Microsoft is still behind the 8-ball when it comes to ARM.

Apparently, in 2016, Microsoft entered into an exclusivity deal with Qualcomm. That's why all official 'Windows on ARM' devices use Qualcomm SoCs. At the time, Apple hadn't yet pulled off its third major architecture shift for macOS, from Intel X86 to ARM.

Looking back, products like the Surface Pro X and the myriad ARM for Windows laptops, were basically built to a budget and for portability above all else. They were never competitive with Intel/AMD-based computers. Microsoft seemed to think ARM would always remain in a niche, only used for light, mobility-first devices.

After upgrading my main workstation to a Mac Studio, I decided to break tradition.

Usually, I sell off my old workstation to offset the cost of the new one. But just last week, Asahi Linux announced their first alpha release.

If you haven't heard of Asahi, it's a Linux distribution based on Arch Linux that aims to bring a polished Linux experience on Apple Silicon Macs (all the current M1 Macs, and any new Apple Silicon Macs that come in the future).

Last month, I built an all-AMD PC to try out Linux Gaming with Steam and Proton, and so I'd have a faster native Linux build machine for my various compilation tasks.

This month, Apple introduced the Mac Studio, and as a now full-time video producer, it was a no-brainer for me to upgrade from an M1 Mac mini.

My Mac Studio arrived Friday, and over the weekend, I spent some time benchmarking it against not only my M1 mini, but also my new AMD Ryzen 5 5600x PC build.

My Mac Studio's specs:

Note: There's a video version of this blog post available here: What does Apple Silicon mean for the Raspberry Pi and ARM64?

A couple weeks ago I tried using the latest Raspberry Pi 4 8 gig model as my main computer for a day, and I posted a video about my experience.

Besides many diehard Linux fans complaining in the comments about my apparent idiocy caused by being a Mac user, the experience taught me one thing: A lot of software still isn't built for 64-bit ARM processors, or even for Linux in general.

But there's one trend that I'm seeing: most of the open source software I use already works great on a Pi 4 running on its 64-bit ARM processor.

Apple Card is not just the physical card you get in the mail when you sign up for an Apple Card. There are a lot of upsides to what Apple's doing with Apple Card and Apple Pay.

I get it. And I also believe the physical titanium Apple Card is a marvel of engineering. Kudos to the metallurgists and designers who produced it—it would easily make for a durable and beautiful display piece on the history of monetary transfer.

The card feels great in your hand. It has a beautiful white finish. The letter and logo detail is impeccable.

The way the magstripe seamlessly integrates into the titanium structure of the card is beautiful, and probably required some extremely precise machining.

I always love when I find a really dumb solution that works reliably to fix a problem that should never really be a problem in the first place. But having worked with audio devices before—though nothing nearly as complex as the AirPods—I am willing to cut Apple some slack in building a seamless aural experience with using AirPods across phone calls, VOIP, iOS devices, Macs, music, and Apple TVs... it's hard to execute perfectly, and as I said in my review of the AirPods two years ago, these little earbuds are as close to perfection when it comes to a wireless sound solution for someone like me.

Anyways, here's the problem:

Sometimes (maybe 10% of the time) when I run vagrant up to build a local development environment for one of my software projects, and I'm listening to music, my AirPods suddenly switch into super-low-quality audio mode. It sounds like you're listening to a song played through a long subway tunnel or something.