# We Rewrote the Ghostty GTK Application

**URL:** <https://ziggit.dev/t/we-rewrote-the-ghostty-gtk-application/11482>\
**Category:** Media\
**Tags:** ghostty\
**Created:** [August 15, 2025, 6:02am UTC](https://ziggit.dev/t/we-rewrote-the-ghostty-gtk-application/11482 "2025-08-15T06:02:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dimdin](https://ziggit.dev/user_avatar/ziggit.dev/dimdin/32/1457_2.png) [@dimdin](https://ziggit.dev/u/dimdin)\
**Post date:** [August 15, 2025, 6:02am UTC](https://ziggit.dev/t/we-rewrote-the-ghostty-gtk-application/11482/1 "2025-08-15T06:02:09Z")

</div>

> **[We Rewrote the Ghostty GTK Application](https://mitchellh.com/writing/ghostty-gtk-rewrite)**

> **Our Zig codebase had one leak and one undefined memory access.** That was _really surprising to me_ (in a good way). Our Zig codebase is large, complex, and uses tons of memory tricks for performance that could easily lead to unsafe behaviors. I thought we’d have a lot more issues, honestly. Also, the one leak found was during calling a 3rd party C API (so Zig couldn’t detect it). So this is a huge success.
> 
> – Mitchell Hashimoto

---

<div class="post-metadata">

**Author:** ![slonik-az](https://ziggit.dev/letter_avatar_proxy/v4/letter/s/ebca7d/32.png) [@slonik-az](https://ziggit.dev/u/slonik-az)\
**Post date:** [August 15, 2025, 10:29am UTC](https://ziggit.dev/t/we-rewrote-the-ghostty-gtk-application/11482/2 "2025-08-15T10:29:42Z")

</div>

I enjoy reading all blog posts from Mitchell. They are always very insightful and informative. This one is no exception.

EDIT: Hacker News discussion [We rewrote the Ghostty GTK application | Hacker News](https://news.ycombinator.com/item?id=44905808)
