zerosleeps

Bugs I’ve encountered in macOS Tahoe 26.2 so far this week:

AirDrop

Attempted to copy a file from one Mac to another. Both running Tahoe. Sending Mac found the receiving Mac without issue, but just said “waiting” when sending the file. The receiving Mac showed no signs that it had been asked to accept anything. Sending Mac eventually claimed the transfer was “declined”.

Liquid glass

Windows and dialogue boxes which use glass effects sometimes don’t show what’s behind them, and don’t refresh when stuff behind them changes. But screenshots of the issue show everything as expected! Difficult to explain in words, so here’s John Siracusa demonstrating the issue.

Phantom windows

Closing a window sometimes leaves behind a “phantom” window. This window isn’t visible, but if it’s on top of something you want to click on, it prevents the click from reaching the right thing. The videos attached to this Firefox bug report demonstrate it nicely.

Problems with AirDrop are exhausting because what’s the point of being in Apple’s ecosystem if shit like that doesn’t work? The other two aren’t major but they smell really bad. And this is the third release of macOS Tahoe.

It’s the 30th of December and I certainly ain’t going to be completing any other books over the next two days, so here are the stats for 2025:

I completed 19 books (same as in 2024, coincidentally) and abandoned another one book. The average rating of completed books was 3.6, which is higher than usual. But I did re-read four 5-starrers.

I discovered one new 5-star book as well: “You Called An Ambulance For What?” by Tim Booth.

The Eclectic Light Company:

Over the last few weeks I’ve been discovering problems that have been eroding confidence in macOS. From text files that simply won’t show up in Spotlight search, to Clock timers that are blank and don’t function, there’s one common feature: macOS encounters an error or fault, but doesn’t report that to the user, instead just burying it deep in the log.

This was a huge component of my 3-month long moan about macOS.

So after my attempt to defend The Bureau of Meteorology‘s new website, we’re being told that it cost $96.5 million.

An experienced, competent, efficient consultant in my industry bills at about $1,000 per day. Let’s be equally generous by assuming one of those consultants works 250 days per year. That means this thing took 386 overpaid-overworked-consultant-years?

That can’t be right.

This a load of shit. The Bureau of Meteorology’s new website is gorgeous and delightfully functional, and it was in public beta for months. Presumably nobody whose bra is now in a twist bothered their arse to check it out or provide feedback when they had the opportunity. That alone earns the teams involved my full empathy, and that of every other developer who knows the frustration.

The federal government has asked the Bureau of Meteorology to fix its new website

It’s not broken.

Environment Minister Murray Watt says the Bureau needs to:

…adjust the website’s settings as soon as possible

Adjust the website’s “settings”? Super helpful feedback for those you’re directing it at, Murray.

And “Northern Victorian agronomist Malcolm Taylor” sounds like a real fucking wild one:

…I would expect some resignation notices over it

Over a website? Jesus.