this post was submitted on 05 Dec 2025
166 points (98.8% liked)

Linux

10441 readers
931 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
 

Mitchell Hashimoto, one of the founders of HashiCorp and lead developer behind Ghostty, a GPU-accelerated open-source terminal emulator launched in 2023, announced that the app has formally become a non-profit project through fiscal sponsorship by Hack Club, a registered 501(c)(3) organization.

In Ghostty’s case, Hack Club now manages compliance, donations, accounting, and public financial transparency. Hashimoto says this structure reinforces Ghostty’s commitment to remaining free and open source, provides legal assurances to users and contributors, and establishes a sustainable foundation beyond any single individual’s involvement.

you are viewing a single comment's thread
view the rest of the comments
[–] arcayne@lemmy.today 2 points 11 hours ago (1 children)

Yeah, complexity is a valid concern. But if your workflow stands to benefit from the performance gains, I'd say it's a worthy trade-off.

The server/client model that Foot uses is actually pretty clever for RAM-constrained situations, especially if you're spawning tons of terminal instances. AFAIK, it's not fundamentally impossible with GPU terminals. Ghostty has single-instance mode on Linux that shares some resources, but the RAM savings aren't as dramatic because GPU terminals maintain texture buffers and rendering state in VRAM per instance.

The catch with Foot's approach is all I/O gets multiplexed on a single thread. That's fine for lightweight usage, but for workflows like mine that involve heavy TUIs and multiple tmux sessions with dozens of windows/panes with big scrollback buffers, it becomes a bottleneck when one or more panes are flooding output from scripts/playbooks/etc.

[–] brucethemoose@lemmy.world 2 points 6 hours ago

Ghostty has single-instance mode on Linux that shares some resources.

Oh I didn’t know this. I will have to try it sometime.

That’s fine for lightweight usage, but for workflows like mine that involve heavy TUIs and multiple tmux sessions with dozens of windows/panes with big scrollback buffers, it becomes a bottleneck when one or more panes are flooding output from scripts/playbooks/etc.

Yeah, for sure. Different use cases. Hence I can keep both installed, heh.