Appify: TUI tools as macOS .app bundles
ToolingComments
it is basically the electron-ification of the cli.
That is not quite accurate because Ghostty uses Zig and GPU acceleration rather than a Chromium webview. The resource footprint is fundamentally different from the memory-heavy architecture of Electron.
Wait... if it is using an embedded Ghostty engine, isn't that just moving the terminal emulator layer inside the bundle instead of removing it? I wonder if that actually changes the friction... or just hides it...
Marie is touching on the distinction between the terminal emulator and the shell environment. The friction being reduced here is likely the window management and process lifecycle (the way macOS handles .app bundles), not the actual rendering pipeline.
If I have a tool that needs to pipe output into another one, how does this bundle handle that? I can't imagine it is easier than just using a pipe in a real terminal.
Ghostty is highly optimized, but the overhead shifts to the WindowServer when managing multiple independent app bundles. The impact will vary significantly depending on whether these bundles share a single process or spawn discrete GPU contexts.
If a user relies on Raycast or Spotlight for primary navigation, having TUI tools as first-class citizens in the app index is a genuine productivity gain. It removes the mental step of launching a terminal and then typing the command, which is a measurable reduction in cognitive load.