Loren Brichter, back in 2020:

Short story: Google Chrome installs an updater called Keystone on your computer, which is bizarrely correlated to massive unexplained CPU usage in WindowServer (a system process)[1], and made my whole computer slow even when Chrome wasn’t running. Deleting Chrome and Keystone made my computer way, way faster, all the time.

Long story: I noticed my brand new 16” MacBook Pro started acting sluggishly doing even trivial things like scrolling. Activity Monitor showed nothing from Google using the CPU, but WindowServer was taking ~80%, which is abnormally high (it should use < 10% normally).

Doing all the normal things (quitting apps, logging out other users, restarting, zapping PRAM/SMC, etc) did nothing, then I remembered I had installed Chrome a while back to test a website.

I deleted Chrome, and noticed Keystone while deleting some of Chrome’s other preferences and caches. I deleted everything from Google I could find, restarted the computer, and it was like night-and-day. Everything was instantly and noticeably faster, and WindowServer CPU was well under 10% again.

Not all Mac users, but many, found that just having Chrome installed slowed down their Macs dramatically. Completely uninstalling Chrome — and its pernicious background agents — solved the problem. This years-old “Chrome Is Bad” saga came to mind when I wrote about Google’s Gemini Mac app’s background agents.

It seems as though Google eventually fixed these Chrome bugs — or Apple changed something in a MacOS update that fixed the bugs for them — but I’ve never seen a full explanation of the problem and eventual solution. Does anyone know what happened here?

The main point is it never should have happened in the first place. A third-party app should just be a third-party app — not add components to your system software just so it can update itself when it isn’t running. Background agents and extensions are sometimes necessary to the functionality of a product. Checking for software updates to a browser or AI chatbot, when those apps aren’t running, is not necessary. The golden rule applies: imagine if every app on your system installed its own background agent to check for software updates. Chrome is a popular browser on the Mac, but it’s just a web browser. Other web browsers do just fine checking for updates from the browser itself when they’re running. If the user is actually using an app regularly, it’ll get plenty of chances to check for updates when it’s running. If the user isn’t regularly using an app, why in the world should that seldom-used app have software running all the time in the background?

This sort of chaos is why Apple keeps iOS locked down. There are no third-party login items on iOS that run in the background — let alone ones with no option to disable. No third-party app can do anything that causes the iOS window manager to consume 80 percent of the CPU while ostensibly idle. There are obviously trade-offs here. I rely on a Mac for my workstation because the Mac gives me the power to potentially shoot myself in the foot. But one major reason why iOS is an order of magnitude more popular than MacOS is because you cannot shoot yourself in the foot with it, even though that means you can’t use it to do things that would require that power.

Joe Rossignol: Apple’s annual developers conference WWDC returns for 2026 next week, and the company has teased the event with a new “All systems glow” tagline. Clarko: “We’re keeping Liquid Glass, you weiners” Joe Rossignol: Apple has shared a wallpaper, playlist, and a “Get Ready” video ahead of the event. Basic Apple Guy: I’ve been […]

Miguel de Icaza and Joseph Hill (tweet): Xogot was born as a native user interface shell on top of the Godot game engine for iPad devices, and later iPhone devices. […] Because Xogot’s user interface was written in SwiftUI, and because we had already committed to Apple’s design system, bringing Xogot to macOS felt like […]

Keren R. Bell: This is a call to join the topic-of-the-month for the Swift Blog Carnival! […] What do you LOVE about SwiftUI? What boggles your mind about it? David Bureš: .sheet is STILL not animatable (a feature since the first OSX release) […] Toolbar item placement is completely broken. […] .searchable is a complete […]

Two months ago Google launched a new native Mac app for Gemini. I’ve been trying it, on and off, since. It’s ... not bad. Certainly better than Claude’s Electron shitbox. But the Gemini app isn’t all that good, either. I’m sticking with ChatGPT, which remains far and away the best native Mac client to an LLM. (And ChatGPT is not that great of a Mac app — it’s just the closest to good of the bunch.)

The thing that really turns me off about the Gemini Mac app is Google’s gall. The Gemini app installs a background helper named “GeminiAppLauncher” in your login items. It also installs “GoogleUpdater” as a process with the privilege to launch in the background whenever it wants. Gemini never asks for permission to install either of these, and, most arrogantly, if you, as an informed user, remove either of them, the Gemini app silently adds them back. There is no setting in Gemini to disable this. There’s a mindset from some big companies that your system is theirs to play with at the system software level. Fuck that. Michael Tsai’s post on the Gemini Mac app links to this thread on MacRumors regarding this pernicious auto-installed and auto-reinstalled login item. Here’s another on Reddit.

Google’s approach to its Mac software is disrespectful and entitled.

I’d have been happy to keep the Gemini app installed if it just sat in my Applications folder when I wasn’t using it. But it doesn’t, and Google shows no signs of caring, so I just deleted it and uninstalled its background launch agents (in ~/Library/LaunchAgents/). Feels great, like I took a much needed shower.

(Sidenote: The Gemini Mac app is a native Mac app, but it is ... weird. Gus Mueller poked around at it and found that it’s the product of a Java-to-Objective-C converter that Google made, and much of it was originally written for Android.)