Ghostty 1.4

Original Article ↗ Hacker News Discussion ↗

Ghostty 1.4, a GPU-accelerated, cross‑platform terminal emulator written in Zig, is winning converts for its low latency, text-only configuration and especially for libghostty, the reusable terminal core now being embedded in IDEs, editors and “agentic” terminals. Commenters weigh it against long‑established tools like iTerm2, Konsole, Kitty and WezTerm, trading off speed, startup time on Linux, feature gaps (e.g. tmux -CC, keyboard‑driven selection, quick-window tabs) and configuration UX. There’s also active debate over modern terminal capabilities such as OSC8 hyperlinks and Kitty graphics—seen by some as essential for rich TUIs and AI workflows, and by others as unnecessary complexity and a security risk.

Purpose of Ghostty and libghostty

  • Many comments say the real “point” is not just another terminal app, but libghostty: a reusable, correct, high‑performance terminal core that other apps can embed.
  • libghostty now covers nearly all of Ghostty’s core, is CI‑tested across many OSes (including freestanding) and has bindings for multiple languages.
  • It is used in IDEs, “agentic” terminals, Emacs (ghostel), custom session managers, and is being considered for other projects (e.g., Neovim, KDE frontend, xterm.js surface).

Performance and behavior vs other terminals

  • Fans report very low latency, smooth TUI rendering, good Unicode correctness and GPU acceleration compared to Konsole, Apple Terminal, and some others.
  • Others find Konsole, xfce4-terminal, foot, st, Rio, etc. faster to launch or “fast enough,” especially on Linux where Ghostty startup can feel slow due to GTK.
  • Benchmarks in the thread suggest Ghostty 1.4 significantly improved speed and memory usage; some still report high memory in certain workloads.

Configuration philosophy and UX

  • Strong split: some love the simple text config and no GUI (“good tools should be invisible; dotfile‑friendly”), others find discoverability terrible without a generated default config or settings UI.
  • Complaints include needing docs just to change fonts or hide an overlay, and inability to paste into the search box on macOS (still unresolved for some).
  • Some want a configuration GUI or at least a TUI; others explicitly value that developer time is not spent on GUI.

Features, gaps, and comparisons

  • Positives: cross‑platform native GUI (Mac/Linux; Windows via libghostty in other apps), built‑in Nerd Font fallbacks, good mouse support with shells like fish, Kitty graphics protocol support, quick terminal / drop‑down style, non‑native fullscreen options on macOS.
  • Missing or contentious: tmux‑CC integration, Kitty‑style hints/quick‑select, advanced keyboard‑driven selection, tabbed quick terminals, restoring full scrollback on restart, better macOS find behavior, Windows GUI build.
  • Some users stick with iTerm2, WezTerm, Konsole, etc., citing more mature features, better GUIs, or less friction.

Security and protocol concerns

  • Debate over OSC8 hyperlinks: modern terminals enable them by default with guarded click behavior; some argue for security‑first defaults (disabled) and note recent OSC8‑related vulnerabilities.
  • Broader concern that rapidly expanding escape‑code features increase attack surface; others counter that bugs should be fixed rather than powerful features disabled.

LLMs and development culture

  • Ghostty’s release notes and core docs are explicitly human‑written; several commenters praise the clarity vs typical AI prose.
  • Elsewhere in the ecosystem, LLMs are used for config editing, bug‑hunting, and even re‑implementing similar terminals, but some users strongly oppose “AI junk” in the terminal itself.