Live data from Hacker News

Ghostty 1.0

ghostty.org

641–650 of 719 posts

Re: Ghostty 1.0

#641
post #629

Earlier quoted context omitted.

These benchmarks are all flawed. You can't measure input latency properly without a camera (or pixel access to the screen but then have to be careful it's not impacting your benchmark). The latency benchmark is just testing VT IO throughput for a specific zsh prompt. Not at all related to input latency. The plaintext IO benchmark is suspiciously slow for both Alacritty and Ghostty relative to Kitty. I ran the same on…

...And you can also cc this your comment to the issues section of the provided repo, so that the author could answer these points and possibly improve their benchmarking process :). --- > I claim it's just "fast" Me, I have three terminal emulators installed on my main machine, alacritty, kitty and xterm. Definitely haven't noticed anything "game changing" (as mentioned in the comment above) from ghostty in this rega…

You could also provide your own terminal benchmarks; that would help Mitchell debug if needed.

Re: Ghostty 1.0

#642

To be honest, I don't "get" ghostty. I am not really seeing how this is so much better than the GNOME terminal that ships with my Linux distro. A lot of people are claiming that ghostty is "faster." I watched the lightning talk where the author claims that catting files and binaries is faster. I tried this against ghostty itself after building with zig build -Doptimize=ReleaseFast, using: time cat ghostty. In GNOME t…

The cool part is that you don’t have to “get” Ghostty, you can continue using whatever you prefer

Re: Ghostty 1.0

#644

I ran into some funkiness once I ssh’d into a FreeBSD box. The shell history was wonky, and goaccess wouldn’t launch at all, complaining about the terminal environment, which I’ve never seen. With that said, this looks like an awesome project and I’ll be following it closely!

https://ghostty.org/docs/help/terminfo#ssh

Re: Ghostty 1.0

#645
post #140

Earlier quoted context omitted.

> kills performance And battery. I gave up on alacritty because it was always using the dedicated graphics card of my MacBook and there was no reasonably way to use the integrated graphics card because it was “low performance”.

- Ghostty does vsync by default and supports variable refresh rates (DisplayLink). If you're on battery and macOS wants to slow Ghostty down, it can and we respect it. - Ghostty picks your integrated GPU over dedicated/external - Ghostty sets non-focused rendering threads as QoS background to go onto E-cores - Ghostty slows down rendering significantly if the window is obscured completely (not visible) No idea if Ala…

can i configure it to run on dedicated? im on desktop, power consumption is not an issue.

Re: Ghostty 1.0

#646
post #560

Ghostty got a lot of hype (I cover this in my reflection below), but I want to make sure I call out that there is a good group of EXCELLENT terminals out there, and I'm not claiming Ghostty is strictly better than any of them. Ghostty has different design goals and tradeoffs and if it's right for you great, but if not, you have so many good choices. Shout out to Kitty, WezTerm, Foot in particular. iTerm2 gets some ha…

Congratulations. On the cross-platform library, I wonder why "libGhostty" and not libTerminal. Which seems like a more appropriate in term of library?

Calling it libTerminal might be confusing. There are other terminal emulation libraries—for example libvterm[1], notably used to power the embedded terminal in Neovim.[2]

[1] https://www.leonerd.org.uk/code/libvterm/

[2] https://neovim.io/doc/user/terminal.html

Re: Ghostty 1.0

#648
post #266
post #173

Earlier quoted context omitted.

TIL. thank you for taking the time to answer - wasnt obvious from above whether or not this was some kind of joke easter egg thing

Same. I have been using this in Yakuake since 5 years but I never knew it was called a "quake mode"

This is especially amusing to me given your choice of terminal.

Re: Ghostty 1.0

#649

The default macOS terminal app has CMD UP/DOWN to move to previous prompts. This is one of my pet peeves about terminal apps, they seem to lack this command?

It works for me with cmd+shift+up/down. I had it set up with the iterm2 shell integration and it just worked.

Just for reference, it looks like it's also bound to cmd + up/down (without shift). Documented as "jump_to_prompt" here: https://ghostty.org/docs/config/keybind/reference#jump_to_pr...

Re: Ghostty 1.0

#650
post #585

Earlier quoted context omitted.

Well it sounds like ghostty is like all the other major GPU terminal emulators (unless you know of a counterexample) and does full redraw, though it appears to have some optimizations about how often that occurs. The power issue might be true in some cases, but even as foot’s own benchmarks against alacritty demonstrate, it’s hyperbolic to say it “kills performance”.

We do a full redraw but do damage tracking ("dirty tracking" for us) on the cell state so we only rebuild the GPU state that changed. The CPU time to rebuild a frame is way more expensive than the mostly non-existent GPU time to render a frame since our render pipeline is so cheap. As I said in another thread, this ain't a AAA game. Shading a text grid is basically free on the GPU lol.

Perhaps that came across wrong, no shade intended, what was meant was that ghostty seems to be like all the other mature GPU based emulators. Which means there's no damage reporting to a display server or anything like that. I don't think it's quite the deal breaker the GGP implies.
Post reply on HN