Urgent.News

What's breaking now, across thousands of outlets.

Tech

Libghostty 1.0: What a Stable C ABI for Terminal Emulation Actually Promises

Twelve and a half million active users got a new terminal emulator this year, and most of them will never know. They did not download anything, and nobody asked them to switch. JetBrains moved the terminal inside IntelliJ, PyCharm, GoLand, and the rest of its IDEs onto libghostty-vt, the terminal emulation library extracted from the Ghostty project, and the usage count in JetBrains' own reporting…

The Libghostty 1.0 release promises a stable C Application Binary Interface (ABI) for terminal emulation, which will enable Linux distributions, IDE vendors, and commercial products to integrate it without reservations. This ABI stability was the primary motivation behind JetBrains' extraction of the terminal emulation library from the Ghostty project and its integration into IntelliJ, PyCharm, GoLand, and other IDEs.

The release was tagged 1.0 by Mitchell Hashimoto, who posted the announcement on Hacker News, where it gained significant attention. The stable ABI promise ensures that binaries already compiled with the library remain functional even when the shared library is upgraded, enabling it to serve as infrastructure rather than being vendored inside each consumer's repository.

Libghostty follows semantic versioning and enforces strict ABI compatibility, primarily through the use of opaque handles and enum-keyed getters and setters. New values can be added to the library by extending enums rather than exporting new symbols, ensuring seamless upgrades without crashing or undefined behavior. The library's design promotes compatibility with various programming languages, including Rust, Go, JavaScript, Swift, Python, .NET, Elixir, Dart, and Java, with community bindings available for over a hundred projects.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why Hindsight Needs Evidence Before Suggesting CI Fixes

Why Hindsight Needs Evidence Before Suggesting CI Fixes Two CI failures can display almost identical error messages and still have different root causes.

  • Hindsight alone insufficient for diagnosing CI failures
  • FlakeTrail incorporates historical investigations for context
  • Recommendations based on verified, failed, and passedunmerged approaches

More from Saturday 7 November →