Ghostty – Terminal Emulator
A modern GPU-accelerated terminal emulator called Ghostty is drawing both enthusiasm and skepticism as developers compare it against established tools like iTerm2, Kitty, WezTerm, and Alacritty. Supporters highlight its speed, native look on macOS and Linux, pane management, and especially the emerging libghostty library that other terminal projects can embed, while critics point to missing or recently added basics (like scrollback search and Cmd‑F), SSH/terminfo friction on remote hosts, and occasional stability or latency issues. Many see its broader significance in how terminals are being reimagined for AI-assisted and TUI-heavy workflows, even as some question whether the hype matches the practical gains over mature alternatives.
Overall reception and alternatives
- Many like Ghostty as a fast, modern terminal on macOS and Linux, but a large contingent still prefers Kitty, WezTerm, iTerm2, Alacritty, or “bare” tools plus tmux/screen.
- Several say there’s no compelling reason to leave iTerm2 yet; Ghostty feels less configurable, less feature-complete, and still evolving.
- Others say Ghostty hits a sweet spot of performance, native-looking UI, and sane defaults; if Kitty didn’t exist, they’d use Ghostty.
Performance: latency, throughput, GPU
- Users report Ghostty as very snappy, especially on heavy output / GPU-accelerated workloads; it competes well with Alacritty and Ptyxis for throughput.
- Input latency is debated: older benchmarks showed poor numbers, newer ones show improvements. Some very latency-sensitive users still feel a delay; others can’t detect any issue.
- Comparisons with xterm, Kitty, WezTerm include tuning tips (e.g., Kitty’s repaint/input delays).
SSH, TERM, and compatibility
- Repeated pain point: Ghostty’s custom
$TERMand terminfo lead to broken full‑screen apps over SSH (e.g.,top,ncdu,less), escape codes showing, or missing 24‑bit color. - Workarounds include installing Ghostty terminfo on remotes, forcing
$TERM=xterm-256color, or using Ghostty’sssh-terminfo/shell integration. - Some argue this is “a bug in servers” hardcoding xterm; others say a terminal emulator should default to well-known term types to avoid requiring remote changes.
- Experiences are mixed: some manage large fleets with zero SSH issues; others find it unreliable enough to stick with iTerm2/Kitty.
Features, UX gaps, and roadmap
- Missing/late features mentioned often: scrollback search, Cmd+F find, scrollbars, stable scrollback, scripting/IPC API, rich notifications, granular colors/UI tuning, tab renaming.
- Scrollback and search exist in nightly “tip” builds and are promised in 1.3; users debate whether to trust nightlies for daily work.
- Ghostty has strengths like quick/quake-style terminal, pane splits with zoom and navigation, minimum-contrast rendering, good font handling and ligature control, native window chrome.
- Some users want deeper Mac-like UX (sidebar tabs, iTerm-style output triggers, better quick-terminal tabs) or KDE/Wayland polish; others prioritize tmux/zellij instead.
libghostty and ecosystem
- The VT/core is factored into
libghostty, already embedded by many projects (desktop, web, “Electron for TUIs”, terminal managers, AI/agent tooling). - Several see libghostty as the real long-term impact: a shared, high-performance terminal core for custom GUIs, browser terminals, cmux-like “terminal managers,” and AI-centric environments.
Project status, governance, and Zig
- Ghostty is now run by a non-profit with public finances and paid contributors; no telemetry is collected.
- Upcoming 1.3 release is said to be imminent with major fixes and features; some criticize the long gap since 1.2.x and unfixed crashes/memory leaks in “stable.”
- Maintaining Ghostty in Zig is reported as positive despite breaking language changes; maintainers rely on LLM “agents” plus docs to handle refactors.
- Some commenters question hype and terminal “tool fetishization,” while others argue that for people who live in terminals all day, these details matter a lot.