Live data from Hacker News

Ghostty 1.0

ghostty.org

601–610 of 719 posts

Re: Ghostty 1.0

#601

Earlier quoted context omitted.

- 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…

> - Ghostty slows down rendering significantly if the window is obscured completely (not visible) About this. For whatever reason, I often end up with foreground windows (e.g. Chrome) covering the background window entirely, except for a sliver a few pixels wide. Would Ghostty handle this case? I don't believe there's any point in full-speed rendering if less than a single line of text is shown, but the window isn't…

We rely on the OS to tell us when we're obscured, and macOS will only tell us if the window is fully obscured (1 pixel showing is not obscured).

Re: Ghostty 1.0

#602
post #64

After a quick test this looks incredibly good and fast. I'll use it as a terminal for the next weeks to see how it goes, but I have good feelings. Thank you so much for writing it. EDIT: WOOOW, for me this is going to be a game changer. I was just working at Redis stuff outputting a ton of debugging info and results, and normally the terminal was the bottleneck, and here instead it printed half million of results in…

Really need scrollback search though. Was a bit surprised it was launched without that.

Re: Ghostty 1.0

#603
post #203

I might give this a shot but using GTK4 makes me think this won’t live up to the “native” claim on Linux. It will likely feel out of place on non-GTK DEs with KDE being the big one. And yes, I did read the about page disclaimer about Linux but strongly disagree about calling GTK4 the closest thing. That’s a very GNOME-centric view (e.g., ignores the rest of the Linux ecosystem) and makes me worry that any issues on o…

Looks really out of place for me on KDE, big fat gnome title bar and buttons etc...

Re: Ghostty 1.0

#604
I have a traumatic experience with GPU-based GUI. Long time ago I tried to run Ubuntu in a VM, and they switched to GPU-based rendering. But as VM doesn't have a GPU, the system fell back to something called "llvmpipe". The result was that the widgets reacted approximately with 30 second lag to every action.

So what I am asking, if you are making a GPU-based rendering toolkit, please write also SIMD software fallback without shaders. Remember how fast Windows 95 was and make it a little bit faster.

Re: Ghostty 1.0

#605
post #56

Earlier quoted context omitted.

https://aur.archlinux.org/packages/ghostty

Note the AUR package was removed because it's since been packaged in the official Arch repos. There is a ghostty-git AUR repo for tracking the main branch: https://aur.archlinux.org/packages/ghostty-git

Will Arch auto migrate the Aur package for me, or should I uninstall and install from the repo.

Re: Ghostty 1.0

#607

Earlier quoted context omitted.

How come TT's categories aren't listed alphabetically?

Do you mean here? https://terminaltrove.com/categories/ (1) Or any other category on the page? (2) We can change (1) alphabetically if that is what you mean.

Yes, those categories. I should have been more explicit.

I found it confusing to look for a category among the unsorted boxes. It would help if they were sorted.

Re: Ghostty 1.0

#608
post #161

Earlier quoted context omitted.

I was using iTerm up until about a week ago when I unboxed a new Mac and decided to test out alternatives while setting it up. Ghostty wasn't out yet so I started with Wezterm, and was shocked to find how much it's speed improved my terminal experience. Typing latency is much better in nvim, and scrolling is vastly improved in nvim and tmux. Ghostty feels like a Mac app like iTerm2 while being fast and having fewer f…

Is iTerm2 noticeably slow? I just use the built in Terminal app and I can’t imagine “speed” being a reason to switch away from it. (There is no lack of speed.)

No, iTerm is not slow. Ghostty is not noticeably faster in any of my workflows. I am sure Ghostty is faster in some use case, but it's nothing I regularly do or have noticed.

Re: Ghostty 1.0

#609

I have a traumatic experience with GPU-based GUI. Long time ago I tried to run Ubuntu in a VM, and they switched to GPU-based rendering. But as VM doesn't have a GPU, the system fell back to something called "llvmpipe". The result was that the widgets reacted approximately with 30 second lag to every action. So what I am asking, if you are making a GPU-based rendering toolkit, please write also SIMD software fallback…

I am asking this in good faith

Why would you not ssh?

Re: Ghostty 1.0

#610

Earlier quoted context omitted.

What is native UI in this context? My terminal emulator is also always basically a full-screen black textarea with white letters. No window borders, no tabs, no buttons, no menus, nothing else. Is there anything native UI would give me in this case (and what is a native UI, I can't find it defined anywhere)?

This gets brought up a lot, so I wrote about it here https://gpanders.com/blog/ghostty-is-native-so-what/

> This also means that native features like pressing Shift+⌘+\ open the tab overview, just as in other applications.

Ah, so this is a macos thing and not just Safari. Can anyone help me select a tab using a keyboard? I use the shortcut, type in the search box and...have to use the mouse :(

Post reply on HN