Interview with Mitchell Hashimoto about Ghostty and Zig

Rust vs. Zig Culture and Evangelism

• Many commenters react to the interviewee’s dislike of “Rust culture,” saying they experience similar discomfort either with Rust, Zig, or both.
• Several report Zig advocates framing conversations as “Rust is bad, Zig is better,” which some found dismissive of concrete requirements.
• Others argue Zig feels far more “culty” than Rust simply because it’s smaller and less “diluted.”
• Multiple people complain about Rust evangelists derailing unrelated threads (“rewrite it in Rust,” moralizing about using non-memory-safe languages).
• Counterpoint: inside Rust-specific spaces, some describe the community as inclusive and beginner-friendly, suggesting outsiders mainly see zealots.
• Broader view: this is just another installment of longstanding “language culture wars” (C vs C++, Java vs C++, Mongo vs Postgres), mixing tribalism, identity, and career anxiety.

Language Choice, Ecosystems, and Tradeoffs

• Several participants like Rust technically but avoid it due to verbosity, “compiler puzzles,” ecosystem noise, or social dynamics.
• Go is praised for “pure Go” libraries, minimal dependencies, and strong tooling; some moved from Rust to Go for a calmer ecosystem and simpler maintenance.
• Rust’s ecosystem is described as heavy on abstractions, bindings, and “horizontal” work (frameworks, layers) with fewer downstream users.
• Zig is seen as minimalist and C-like; some appreciate that it rejects feature creep even at the cost of missing conveniences.
• Memory safety is widely valued, but some argue that for many applications a GC language is a more appropriate tradeoff than Rust’s ownership model.

Ghostty, Hashi Tools, and Forking

• Opinions on Ghostty diverge: some find it buggy with fewer features than mature terminals; others call it the best, fastest emulator they’ve used, with no noticeable bugs in daily workflows.
• HashiCorp tools are called both “overrated” and “game-changing.” Terraform and Vault are cited as widely used, especially on-prem and in high-assurance environments; others rely entirely on cloud-vendor secrets instead.
• On forking Ghostty or similar projects, one side notes that ongoing synchronization with upstream is as hard as maintaining feature flags.
• Others think better tooling—possibly AI-assisted—could make long-lived forks and “federated” variants more practical.

Shells, Structured Data, and Terminals

• Debate over CLI output: some insist CLIs should default to plain text for easy piping; others prioritize JSON or structured data for robust automation.
• PowerShell is praised for structured pipelines but criticized for clunky UX and backward incompatibilities.
• Newer shells that treat JSON as first-class are cited as promising examples of richer terminal workflows.