“Unfortunately, price increases are unavoidable,” he said. “We’re doing our best to mitigate the huge increases that are being passed to us, and we’ve been trying to shield our customers from the increases, but the situation has become unsustainable.”….
“There’s less supply at a time when consumers want devices and the memory guys are passing along huge price increases,” said Cook. “We definitely need memory pricing and supply to return to reasonable levels for consumer products. That’s the bottom line.”
Cook called the current supply situation, driven by wild buying in the AI industry, “a hundred-year flood,” and that he had “never seen anything like it in any area in over 40 years.”
I do wonder how Apple will raise prices. An informal guess is that a lot of cheaper base configurations will vanish, that new models will start at higher prices, that Apple’s rumored OLED touchscreen MacBook Pro models will set all-time high starting prices, and that Apple will do everything it can to keep a lid on the prices of its base models across the board. The big question is, will the MacBook Neo jump up in price, and if so, by how much?
That’s an Apple News+ link. Here’s the web version. ↩
Under the watchful eye of Steve Jobs, the Apple II takes form at last. It’s an integrated color computer created by Steve Wozniak, powered by a groundbreaking power supply designed by Rod Holt, and wrapped in a plastic shell designed by Jerry Manock.
James Chang has built a project that upgrades the file-sharing stack on Apple’s long-discontinued Time Capsule hardware so that it will work on modern OS versions:
This is a modern Samba setup that runs directly on the Time Capsule itself; macOS 27 can connect to the Time Capsule as a network share, and use it for Time Machine backups…
You get the full Apple experience reproduced: after you install this, you do not have to worry about it again, even if the device IP address changes. It will show up automatically in Time Machine in settings app, and it will use mDNS/Bonjour so it will work fine even if the IP address is not static and gets changed.
It’s a clever piece of work that uses a very specific version of Samba and some other software running on a tiny RAM disk with other files stored on the device’s storage partition. I don’t have a Time Capsule to test this myself, but if you have one and have been lamenting its retirement, think again!
Back from WWDC, Jason and Myke have had more time to think about Apple’s announcements—and to try many of them in beta releases. Siri AI impresses, we have Snow Leopard vibes, and much more.
I have a Mac Studio M2 Max with 32 GB of RAM and a 1 TB SSD in front of me. While not the most powerful personal computer you can purchase today, it is among the most computationally capable ever made—a vastly capable machine. So why do I have to wait for typing to catch up with me and see a rainbow spinner on the regular?
I’ll tell you why: iCloud Drive and Spotlight. Apple lacks any transparency about how iCloud Drive works or fails. The same is true of Spotlight. These big black boxes churn away, performing a million billion operations a day, and we don’t know exactly what they do. That’s not me being conspiratorial: I honestly don’t care what’s happening under the hood—until it breaks. Without diagnostic tools, even someone like me, ostensibly an expert, can be completely at a loss and waste many hours.
I wrote “Cloudy with a Chance of Insanity: Unsticking iCloud Drive” for TidBITS back in October 2023 about a multi-month odyssey with Apple technical support in trying to dislodge unsyncable files.1 That problem has barely surfaced since—an 80K file will sometimes get stuck for a while—and I thought Apple might have really solved syncing, at least as exhibited on my Mac. I receive dramatically fewer emails about iCloud Drive than I used to, which is another data point.
But Mr. Edge Case here can always find a way to break something.2 I’ve been working on a large manuscript for my upcoming book, Flong Time, No See, a revised and expanded collection of researched articles I’ve written about printing and type history over the last several years.3 I pasted in text that was typically copied from Web pages, and wound up with over 250 footnotes.
While putting together the files for this book, Apple released its Creator Studio system, and shipped Pages 15. After having no problems, I dutifully switched over. This was months ago, and as I continued to work on this reasonably large file—weighing it at about 60,000 words now—everything seemed fine.
A few weeks ago, however, I started to experience system slowdowns. Pages was taking up 12 GB of system memory! System load went through the roof! CPU consumption was outlandish! All signs pointed to corespotlightd, a long-time enemy of performance. That daemon handles background indexing for Spotlight, and the slightest thing wrong in a file or directory, or perhaps due to mild corruption in its underlying files, turns it into a rampaging beast that eats processor cycles like I consume potato chips.4
There’s a well-known procedure for killing this beast, though another is spawned from its remains: stop the index, delete the index files, restart, and re-enable indexing. From the Terminal, use these commands. Make a backup before proceeding. Take extreme care with rm -rf, as a misstep in entering or copying can wipe out files!
sudo mdutil -a -i off
rm -rf ~/Library/Metadata/CoreSpotlight
You can use Restart from the Apple Menu while holding down the Option key (to avoid being asked), or you can take a shortcut from Terminal, assuming you have ensured all files are saved:
sudo reboot
After your Mac restarts, go back to the Terminal and re-enable indexing:
sudo mdutil -a -i on
For many (perhaps most) people, this solves the problem. For me, it just delayed it. With some isolation using System Settings: Spotlight: Search Privacy, I added specific folders, such as mail archives, since that seemed like it might be part of the problem.
Search Privacy lets you exclude volumes and directories from Spotlight indexing, which can remove unwanted results and sometimes (only sometimes!) reduce thrashing.
One piece of advice I found suggested that if I thought Pages was the problem, I should exclude the iCloud Drive path containing Pages files. Fine! I clicked the plus icon in Search Privacy, pressed Command-Shift-G to bring up the path dialog, entered ~/Library/Mobile Documents/com~apple~Pages/, and clicked Choose. This seemed to work for a while, then nothing availed.
Finally, after analyzing logs and caches, the culprit was clear. It was not that large a Pages file: every time I saved, Spotlight’s worker bee was performing excessive re-indexing that consumed gigabytes and one or more processor cores. Moving the file to a local directory (in my Documents folder) while editing eliminated the problem. It also freed up space, as the temporary Spotlight indexes and Time Machine snapshots had become absurdly large.
289 footnotes seem to be fine for Pages, but Spotlight and iCloud Drive find them hard to swallow.
What could Apple have done to help here? This is where I would hope machine learning, coupled with some interactive code- and system-expertise bots, could help:
Note that a system component is acting well outside known parameters.
Identify CPU usage that is tied to Apple-owned processes.
Provide a troubleshooting tool, even suggesting it in notifications.
Create human-readable logs that don’t require system administrator knowledge to interpret.
In the case I describe above, an Apple-created daemon was rampaging out of control due to a single identifiable file!—cascading into other problems. It should be solvable by Apple. The fact that we have more power under the hood by orders of magnitude in the past, coupled with neural cores in the CPU packages, just makes this even more embarrassing. Solve Siri, Apple, yes, but real transparency and troubleshooting in macOS would also make a big difference.
[Got a question for the column? You can email glenn@sixcolors.com or use/glennin our subscriber-only Discord community.]
I should have made an unsinkable/unsyncable pun in the title, but there is an esprit d’escalier moment for everything. ↩
An “edge case” is something that is often considered unlikely to occur with a product, whether software, hardware, or mechanical. Yet, no matter how much I’m just trying to get something done, I apparently trigger edge cases all the time. Software companies “love” me for this. ↩
Flong is a kind of paper-like mold that was extremely useful during the days of metal-based relief printing. Of course, you can pre-order a copy to get the full scoop! ↩
Adam Engst at TidBITS took the time to extract every item on the WWDC 2026 keynote slide that captured our attention last week. Even better, Adam grouped the changes into operating systems, apps, and other categories. While the 27 OSes dominate the list with improvements and revisions, you can also note how many changes Apple is making to Photos and Shared Albums, Find My, Music, and a number of other across-the-ecosystem tools.
Then Marcin Wichary used Adam’s post to slice the data in a different way, counting the number of times the slide used words like fast (59 times) and reliable (22 times). Marcin reasonably argues that speed is the easier problem to attack, while reliability is fuzzier and much harder to pin down.
It’s WWDC week and John Moltz had the temerity to go on vacation, which means it falls to me, his dutiful editor, to file something. Also, Jason’s on the road somewhere, so really, there’s nobody to stop me. The power is intoxica—wait, is this zero-proof power? Rats.
Anyway, down to business.
If you take away anything from this week’s WWDC, it’s that Apple and Google are just friends. Plus, Siri is good now, and Tim Cook says “good byyyyyye.”
After three days of that, you too might wake up alone and cold on the Rainbow Stage, a blown-up printout of a wall of features slide covered in red pen and incomprehensible scribblings plastered to your face with drool.…
My thanks to Unite Pro for sponsoring Six Colors this week.
Safari web apps and PWAs are a nice start, but they’re limited. Browser tabs are messy. And most tools for turning websites into apps still feel more like wrappers than real Mac software.
Unite Pro takes a different approach. It turns any website into a fast, isolated Mac app built specifically for macOS — with support for Window, Sidebar, and Menu Bar modes, deep visual customization, smart link forwarding, and native enhancements like dock badges, meeting alerts for Google Calendar and Outlook, AI overlays for ChatGPT, Gemini, Grok, and Claude, and more.
What makes Unite Pro special is how much control it gives you. You can remove distractions, force dark mode on sites that don’t natively support it, apply custom scripts and styles, and shape each app around the way you actually work — while keeping sessions, cookies, and permissions separate from your browser.
Six Colors readers can get 20% off Unite Pro this week with the code SIXCOLORS. Learn more and download at bzgapps.com/unite.
Apple's pattern of updates is often described as two beats, maybe like the lub-dub sound of your heart: a year of big changes, followed by a year of tweaks that feature just a couple of marquee improvements.1 The 27 series of operating systems marks a big dub year, but there's a backbeat to the rhythm, too, as Apple retreats from what most of us believe were overreaches in the interface department.
Liquid Glass was not beloved. I didn't mind it so much on the Mac, and I found some iPhone and iPad improvements worthwhile, and the rest tolerable. Some people hated it. John Gruber notably decided to hold off on updating his primary Mac to Tahoe. Apple ironically highlighted a slider in its WWDC keynote that one could describe as "mostly forget about Liquid Glass," with an option from "full-on, nobody wanted this" to "as close to zero as we can go without breaking the interface." Good.
No (Tahoe, button, left). Yes (Golden Gate, slider, right).
Stacey Ford, Apple's Vice President of OS Program Management, called out a broad mandate in the keynote. "We scoured every part of the OS for opportunities to refine our systems from the UI to the foundations," she said. "Nothing was off limits, no enhancement too small." In other words, there are no sacred cows leftover from the design team that left, and maybe Ford and her group hate the same things that we do, and they've been given the authority to fix them.
Maybe as a consequence, Liquid Glass will improve legibility through several changes, which you'll see even with the slider set to zero. The layers of Liquid Glass elements will now be rendered so that the diffusion of the underlying material won't interfere as much with legibility. When content moves beneath a floating bar, the bar will now—shocking!—float on top and increase contrast to keep its contents comprehensible, too. Edges will now be darker, and icons sharper.
This year, those are Siri AI, Apple Intelligence integration more generally--and maybe child-related safety and app-usage tools? ↩
I mean, the way that we have designed Siri, Siri really wants to say ‘Listen, that’s not what I’m here for, right? I’m here to help you. I can help you get things done. I can help you learn about the world.’ But if you try to engage Siri as a romantic partner, Siri’s not up for that. Siri’s 100 percent not into that.
This jibes with what I heard from my conversations with Apple this week, namely that Siri is designed to act as your helpful personal assistant. It’s further borne out by the poking around that folks like Federico Viticci have done in what they can find of Siri’s prompts.
This isn’t to say that Siri doesn’t still occasionally dip into the kind of AI speak that we’ve grown accustomed to from chatbots; I’ve definitely seen it. But I’ve also noticed, anecdotally, that Siri is quick to acknowledge mistakes and, crucially, ask for more followup information rather than doubling down. If nothing else, that feels like a key difference that I want to see from my AI interactions.
Our hopes for fixes in the ’27 platform updates, what we’ll do with our Intel Macs now that they’ve reached end of the road, whether we’ll trust the new Siri AI, and how we feel about Apple’s child safety and age verification answers.
I look at the content creators who are possibly experiencing their first WWDC, and realize: how am I still here, and still taking notes on an iPad, while these younger folks are shooting videos that millions of people will watch? I’m in between changes again, but I don’t mind it. The challenge still feeds me. I’m more comfortable now, but – miraculously – I don’t feel cynical or jaded. Some people are into that sort of attitude; I’ve always preferred to put in the work to be critical and enthusiastic about the things I like. In a world of complaints, optimism is a skill.
This was, um, 30 years of me covering WWDC. If Federico is now a veteran, please do not tell me the word for what I am. But I really enjoyed his reflections and the ongoing (yes, even for me) challenge of adapting to change, seeing things with fresh eyes, and appreciating the people who are experiencing these events for the first time.
In a preview of our new Designed in California podcast, we travel to the summer of 1976, as Apple travels to Atlantic City for a computer trade show, the Apple II begins to form, and the fellowship between the two Steves shows signs of breaking.
