Jeff Johnson:

In today’s macOS 26.3 update, Apple implemented a “fix” for an issue I blogged about a month ago, macOS Tahoe broke Finder columns view. (At the behest of John Gruber and the Apple Style Guide, I’m now using the term “column view” rather than “columns view.”) Specifically, the issue was with the system setting to always show scroll bars. [...]

Without the path bar, the columns are now taller, but the vertical scrollers remain the same height as before, leaving vertical gaps, a ridiculous amount of space between the bottom of the scrollers and the bottom of the columns, looking silly and amateurish.

Did nobody inside Apple test this configuration either? Or do they simply not care?

In one sense, this whole issue with column view in the Finder with scroll bars set to always show is a little thing. It was downright broken in earlier versions of MacOS 26 — you literally could not resize the columns. So now it’s not broken. But as Johnson says, it looks silly and amateurish.

This is the sort of detail that Apple used to strive to get pixel-perfect, all the time, for all settings. “Whatever, good enough” instead of “insanely great”.

Andrew Cunningham, writing for Ars Technica at the end of January:

Apple also outlines a number of usage restrictions for the generative AI features that rely on external services. Apple says that, “at a minimum,” users will be able to generate 50 images, 50 presentations of between 8 to 10 slides each, and to generate presenter notes in Keynote for 700 slides. More usage may be possible, but this depends on “the complexity of the queries, server availability, and network availability.”

Steven Troughton-Smith, last week, after creating an entire app with OpenAI’s Codex:

This entire app used 7% of my weekly Codex usage limit. Compare that to a single (awful) slideshow in Keynote using 47% of my monthly Apple Creator Studio usage limit 👀

Something feels off here, by at least an order of magnitude (maybe two?), that creating an entire good app costs way less than creating one shitty slide deck in Keynote. It should be the other way around.

Connecting user accounts to third-party APIs always comes with the same plumbing: OAuth flows, token storage, refresh logic, and provider-specific quirks.

WorkOS Pipes removes that overhead. Users connect services like GitHub, Slack, Google, Salesforce, and other supported providers through a drop-in widget. Your backend requests a valid access token from the Pipes API when needed, while Pipes handles credential storage and token refresh.

Simplify integrations with WorkOS Pipes.

Simon Willison:

OpenAI just released a new macOS app for their Codex coding agent. I’ve had a few days of preview access — it’s a solid app that provides a nice UI over the capabilities of the Codex CLI agent and adds some interesting new features, most notably first-class support for Skills, and Automations for running scheduled tasks.

Interesting, for sure. But super-duper interesting? I don’t know.

Apple Newsroom:

Xcode 26.3 introduces support for agentic coding, a new way in Xcode for developers to build apps using coding agents such as Anthropic’s Claude Agent and OpenAI’s Codex. With agentic coding, Xcode can work with greater autonomy toward a developer’s goals — from breaking down tasks to making decisions based on the project architecture and using built-in tools.

I don’t know if this is super-duper interesting news, but I think it’s super-duper interesting that Apple saw the need to release this now, not at WWDC in June.