zerosleeps

From the Apple Support Community landing page:

The Apple Support Community will permanently close on November 20, 2026. Starting today, the site will no longer accept new posts and is available in a read-only state.

Good. It’s been causing nothing but damage and frustration for years. Every time I investigate some annoying macOS issue a thread from this thing is inevitibly at the top of every search, because apple.com, but the thread is always utterly useless.

Jason Snell says it best:

These message boards were an embarrassment for Apple. Not only were they very much out of step with what the web has come to be over the last couple of decades, but their presence under an apple.com domain meant that they ranked highly in search and were perceived by the general public as being official in some way.

But they weren’t, nor were they helpful. They were full of people asking questions and not getting useful answers, with many responses given by users who were more motivated to gain karma in the forum’s user-ranking system than to help. I can’t tell you how many times I visited these forums while trying to track down the answer to a peculiar quirk or bug, only to find the (legitimate!) question being shut down by an officious high-ranking know-it-all who didn’t actually understand what was being asked and couldn’t provide a useful answer.

And here’s Jeff Johson with a punchier but very relatable observation on the lack of input from Apple on this soon-to-be-defunct service:

Apple sits back like fucking dummies, ignoring problems that everyone knows exist because nobody bothers to fight through the red tape of supplying Apple with the required information including sysdiagnose and TPS reports via Feedback Assistant.

I don’t think I’ve heard about Goodhart’s law before. It’s a good one. I was introduced to it in this post by Ibrahim Diallo who muses:

We spent astronomical sums of money to build AI because we believed it was valuable. Now, we must prove it is valuable simply because we spent all that money.

Like everyone else does, and in violation of my concerns about handing my browsing activity over to an advertising company. The number of paper-cuts I’m getting from using Firefox has crossed a line for me though.

The tantrum you’re currently reading was prompted when I triggered bug 1890697 a few moments ago. Now this isn’t entirely Firefox’s fault, but it is the only mainstream browser which behaves this way when opening developer tools. I encounter it every single day when I’m working on the ridiculous web application I maintain at work.

Next on the list is bug 1941693, which destroys my Mac’s battery life when watching full screen videos. This is also an every day occurrence.

Those are the big ones, but I could list a dozen other stupid things I run into almost every day. A lot of them are specific to the way macOS does things and it therefore does feel like macOS is way down the list of Mozilla’s priorities. Which is fair enough - they can do what they want - but Mac people like polish and Firefox fails in that regard.

And look, I don’t give Mozilla any money and they don’t owe me anything. Quite the opposite in fact: as a developer I should be contributing, but I don’t even know where to begin with the Firefox codebase. I’m a web developer for crying out loud!

It’s a sad situation but once I tune out the Google-ness from Chrome it’s the only mainstream browser that gets out of my way.

From the Python 3.15.0 release announcement on Python Insider:

To celebrate the new 3.15, Barry Warsaw has a present for us!

I had this idea to whip up a little TUI adventure game that takes you through a What’s New in Python 3.15.

…

The easiest way to play it is to run:

uvx --python 3.15 whatsnewt

Barry Warsaw is a core Python developer, and Python Insider is an official Python blog. That is… kind of an official endorsement for Astral’s uv!

Oh here we go a-fucking-gain. This time it’s a process called “dasd”:

It’s been like that for hours. log stream and log stats show this process spewing the same 30-ish lines into the system log at a rate of about 180 messages per second. Something about running ArcadeResetPO over-and-over. What is ArcadeResetPO? Not a clue. What is dasd? No idea:

% man dasd
No manual entry for dasd

At least this time I don’t seem to be the only one with this problem, and there are even suggested workarounds.

I have the same questions that I did with mediaanalysisd: what is this stuff doing (when it works) that benefits me? I assume it’s something to do with Apple Arcade, a service I have never used and have no interest in. My Mac isn’t even signed in to iCloud.