mogging AI with the triple em-dash ⸻ your move claude

Attention to detail: I think no user has ever complained about this, but half of our team are self-appointed flicker police 👮🏻‍♂️

A good case study in how, no matter how much you test, some users will have setups you never covered. The only way to get everything about Apple Shortcuts (icons, whether they take input) is Apple Events, and fetching them one shortcut at a time cost ~60ms per shortcut. @stephenrobles has 2400 shortcuts. At 60ms each that's 144s, past our 120s timeout, so he saw nothing. Batching plus cheaper icon conversion got us to ~6ms per shortcut, and ~1ms once icons are cached.

As part of this week's release of @raycast I shipped a bunch of improvements related to colour contrast adjustments. Let's look at the challenges Raycast faces and some examples of how we tackle them…

Wild RunningBoard/WebKit bug If a @webkit helper process (Networking, WebContent or GPU) gets a PID that RunningBoard retired moments earlier, RunningBoard keeps saying the live process "does not exist". WebKit reacts by suspending it, and nothing wakes it up again. Result: pages that never load, or a frozen blank window, until you relaunch and get luckier PIDs. Here it is reproduced in @conductor_build a Tauri app: window stays blank after app restart..

macOS 27, so far so good

I have the weirdest bug in Codex @OpenAI. I can't open a Terminal with ⌃` and even worst the setting doesn't even appear in Keyboard shortcuts. The menu bar item is also no-op, help

Most played games, CSS being probably far ahead in hours played

Traffic light buttons are getting wilder every day on macOS 27 🚥

Introducing 𝚂𝚖𝚘𝚕𝚕.𝚊𝚙𝚙 - 38 KB native web browser - 20 MB of RAM for the host - 95 lines of Objective-C (no Swift because objc is faster and smaller) - no features because they use memory and create clutter - no URL bar because the focus ring alone was 2.5 MB of CGImage plus 1 MB of CoreAnimation layers - title bar kept, reluctantly (4 MB), because I want to be able to move the window

SwiftUI vs. AppKit on macOS, using a deliberately naive approach for each: SwiftUI → 𝚃𝚊𝚋𝚕𝚎 + @𝙾𝚋𝚜𝚎𝚛𝚟𝚊𝚋𝚕𝚎 array of 𝙸𝚍𝚎𝚗𝚝𝚒𝚏𝚒𝚊𝚋𝚕𝚎 rows AppKit → 𝙽𝚂𝚃𝚊𝚋𝚕𝚎𝚅𝚒𝚎𝚠 + data source + 𝚒𝚗𝚜𝚎𝚛𝚝𝚁𝚘𝚠𝚜 Same log stream, very different performance.

All I want is an iPhone 18 Mini, I don't need aperture

Playing a bit with iPhone Duo style hinge animation on a MacBook Not worth an app, but love the gimmick.

- you're being real right now? - I'm always being real

macOS 27 introduces a new `NSWindow.StyleMask` to add a Liquid Glass frame to the window (bit 36). By default that glass is flexible, when dragging the window content it stretches 🫪 Under the hood it uses an `NSGlassFrameView`, subclass of `NSThemeFrame` which is the commonly used class for window frames. Note that I haven't seen used anywhere but it's ready to be implemented for `NSAlert`.