Vibing a non-trivial Ghostty feature

Original Article ↗ Hacker News Discussion ↗

Ghostty features and usability

  • Many like Ghostty and consider switching from other terminals, but several “fundamental” gaps block adoption: missing Cmd-F search, scrollbars, drag-and-drop on KDE, and some SSH/terminfo quirks.
  • Search is on the roadmap (v1.3, 2026); one commenter implemented a rough search prototype and was surprised by the complexity, especially with streaming output.
  • Users note default scrollback is small but configurable. Some have reverted to Warp or other terminals because Ghostty still feels barebones.

AI disclosure and “vibing” terminology

  • Ghostty now requires contributors to disclose AI-assisted code in PRs, seen as a responsible practice.
  • Several argue the post’s workflow is “AI-assisted” or “vibe engineering,” not the original “vibe coding” caricature of shipping unknown slop.
  • Others note the title intentionally baits both pro- and anti-“vibe” extremes to showcase a more disciplined pattern.

How developers use coding agents

  • Many use agents to get past the “blank page” (zero-to-one) stage, scaffold UI code, or handle tedious boilerplate and repetition, especially with complex UI frameworks.
  • A common pattern: generate, then heavily review or even throw away the code, keeping only ideas or structure.
  • Some rely on agents for refactors instead of LSPs; others remain wary and review every line.

Quality, “slop,” and team dynamics

  • A recurring complaint: coworkers flooding teams with low-quality AI code while claiming huge productivity, making honest critique politically risky.
  • Suggestions include focusing on code quality rather than tools, using AI for PR review, and instituting stronger quality gates.
  • Skeptics question whether measured productivity gains exist versus just a feeling of speed.

Productivity, learning, and personal preference

  • Experiences diverge sharply:
    • Some find starting hard and iteration easy; others are the opposite.
    • Some love the craft of writing code and see AI as trivializing or ethically problematic; others are outcome-focused and happy to outsource tedium.
  • There’s concern that over-reliance on AI impedes developing zero-to-one skills and that prototypes built with LLMs are further from production-ready than they appear.

Tools, ecosystems, and wider impacts

  • Amp (agentic CLI) draws interest; some see it as the strongest vendor-neutral option, though it can be costly vs. bundled “Pro” subscriptions.
  • Environmental costs of heavy inference and “AI to create and then destroy code” are briefly debated.
  • Broader outlook: vibe-style development is seen as inevitable; businesses will choose “good enough” automation, potentially eroding the perceived value and pay of human software developers over time.