I briefly emulated it with UTM (QEMU) on macOS; the host was an M1 series chip. This story is the first indication that I might run Haiku on that machine's bare metal someday.
It's a delight to use, if a little esoteric at first. After the experiment phase, the software ecosystem comes up fairly limited. But I recommend visiting.
Because they're the main prompt injection vector, I think you'd want to distinguish tool results from user messages. By the time you go that far, you need colors for those two, plus system messages, plus thinking/responses. I have to think it's been tried and it just cost too much capability but it may be the best opportunity to improve at some point.
Gotta meet your audience where they are. As a Mobile Safari user, the foremost way I feel my use of the web is crippled is that pages assume a bigger screen or are just poorly arranged.
This of all web pages ought to be easy to read on an iPhone screen, but the way it's constructed prevents it. You can't zoom the whole page out to see the entire table width because the table is in a scrolling frame and wider than its box. You can only scroll the nested frame sideways to see how row labels relate to iPhone cells. If you give up and use landscape, it still scrolls vertically in its frame. You have to aim for the margin or else you'll scroll just an inch and be halted because you caught the table.
Because it's critical that the web be as free as it is:
• It's natural that some pages turn out like this
• So it's natural the web is a little bit shitty all over
• So it's natural the demand for richer web features is low
Just having watched the video, the session setup, close, and launch seem tied to the idea of a single window per app. Is that right? What kinds of workflows is this explicitly meant vs. not meant to support?
The way a user switches window sets with backtick and app windows within them with tab is inverted from the usual major and minor shortcuts. Normally you switch apps with tab and windows within them with backtick, or in the case of stage manager, you switch window sets with tab and windows within them with backtick. As a default I think the keys make less sense than they could.
> …requires an account holder to indicate the birth date, age, or both, of the user of that device…
The way I read that, you just have to ask for an indication of age. Like when I'm not logged in to Steam and I want to look at a game with blood, it asks for a birth year and I pretend to be 109. That's not exactly "age verification." Am I missing something?
Why make a desktop windowing system app, for a user group who runs a bunch of simultaneous terminal sessions with tear-off tabs or tmux panels, and then force everything into one window that can only display a single session at a time?
The Open button and then codex resume --last is good, but it's a waste and The Wrong Abstraction not to make instantiable conversation windows from the get-go.
I wrote this a long time ago, but I think the metaphor was about generative AI applications vs. traditional software applications, not about AI coding agents vs. writing code yourself.
Hi, that's my website and my wisecrack article. It was a while ago, but I think the metaphor was that a train is traditional deterministic-ish software, whose behavior is quite regular and predictable, compared to something generative which is much less predictable.
Native performance doesn't earn that much user goodwill without native layout and behavior. You can't make a single design for many platforms and please everyone who chose each platform for what it is. Unless perhaps you are Snap and having a _unique_ UI is part of the appeal for your young-leaning audience.
Shell commands and files on disk are the classic narrow waist, and this type of tool, exemplified by Claude Code, locates a coding agent down in that ecosystem.
Why shouldn't you be able to use the abilities of this tool as a batch command, connected with all your other basic tools, in addition to interactive sessions?
Cursor's chat being locked in an IDE sidebar has felt like driving with a trailer attached. For some tasks the editor is secondary or unnecessary, and as a papered-over VS Code fork, Cursor has a lot of warts that you just had to accept. Now you can just use your favorite editor.
Companies make apps but want to be platforms, so they try to put everything in one app and help you forget about everything else. VS Code and Figma, for example, make their own extension ecosystems rather than connecting outward, because it makes them platforms-as-apps and harder to leave. But a desktop task workflow spans many apps and windows. You compose it yourself to your needs. We are computer users more than app users.
To me as a computer user, a tool that's compact and has compatible outward extension points feels good.