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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Bias warning: I spend most of my workdays in the terminal, and I'm also a contributor to Ghostty.
The most noticeable difference is smoothness when you're doing intensive terminal work like scrolling through large log files, running TUIs like btop/lazygit/yazi/lnav, or using multiplexers like tmux with multiple panes. Without GPU acceleration, you'll see stuttering and lag with heavy output or complex interfaces.
It also makes a big difference in editors like Neovim, especially with syntax highlighting in large files or when scrolling quickly through code. The rendering just feels snappier and more responsive overall.
Basically, if you spend significant time in the terminal (like I do), the improved responsiveness is immediately noticeable. If you mostly use it for basic shell commands, the benefit is negligible.
Long as we've got an expert here (not sarcastic, this is cool insight, thank you) what's the downside?
Like daq mentioned, reduced battery life is one downside if you're on a laptop. RAM usage is also higher, usually 50-100MB more per instance than traditional terminals (sometimes more depending on the terminal and your config).
In terms of Ghostty specifically, it's still a fairly young project, so the chance of hitting an edge case issue is higher than if you were using a more mature GPU-accelerated terminal.
One downside on a laptop is reduced battery life.
I tried Ghostty briefly before, but you have to really try hard to notice preformance difference over Konsole.
Cool idea, but not useful for those that spend all day in a terminal imnho.
I am not the expert, but… Complexity?
Sometimes I use Foot instead of Alacritty/Wezterm to save RAM in extreme situations. Foot's also really nice because it uses a server/client model (again, saving RAM with many terminals), though I don’t know if that’s fundamentally impossible with GPU terminals.
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.
Oh I didn’t know this. I will have to try it sometime.
Yeah, for sure. Different use cases. Hence I can keep both installed, heh.
Oh, thanks! I have lazyvim, btop, and Musikcube already, but I've never tried them in something like Ghostty or Alacritty. Might be worth trying!
Also, I'll be looking into some of those programs you mentioned!