Live data from Hacker News

Ghostty 1.0

ghostty.org

131–140 of 719 posts

Re: Ghostty 1.0

#131
post #30

For those who don’t have the background: - created by Mitchell (founder of HashiCorp) - it’s developed in Zig (and Mitchell recently pledge $300k to Zig foundation) - uses native UI (which is super rare for cross platform app) - amazingly performant. e.g. https://hachyderm.io/@mitchellh/111919642467789362 - has lots of amazing small details like below https://hachyderm.io/@mitchellh/113330304084905500 https://hachyde…

It doesn't work in Windows so how is it cross platform? Also, I've been using terminals since DOS in 1990 and never once have I had to say, "I wish this terminal had more performance", so I'm not sure that performance is really relevant here. If I write a command to build my project which takes 10 mins to build, does it matter whether the terminal command ran in 10 milliseconds vs 1 millisecond? In the linked speed d…

are you still running DOS too?

Re: Ghostty 1.0

#132
Just want to share what I just realised, but the author is no one else than the mitchell hashimoto from hashicorp, so not exactly a newbie ! Would it have killed you to let us poor 99% have a bit of fun releasing useful projects too? (And also reach a bit of your determination, skill and talent)? (no, really, kudos, well done and thanks)

Re: Ghostty 1.0

#133
post #35
post #34

[flagged]

How many platforms are required? I noticed it doesn't have an OS/2 download.

I think it’s both fair to say Linux and Mac make something cross platform, but it’s also very reasonable to expect Windows as well given its massive install base size.

Re: Ghostty 1.0

#134
post #28

> For example, on macOS, Ghostty supports Quick Look, force touch, the macOS secure input API, built-in window state recovery on restart, etc. These are all native APIs provided by macOS that don't have equivalents in Linux desktop environments. I believe window state recovery has some approximate equivalent in GNOME and KDE, but maybe not exactly the same (and I don't know how easy it is to integrate with).

On X11, Gnome and KDE Plasma supported session/state restore, but this was based on XSMP and couldn't be simply reused for Wayland. There's an ongoing standardization effort to provide equivalent functionality for Wayland: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m... KDE Plasma provides a "fake session restore" for the time being: https://invent.kde.org/plasma/plasma-workspace/-/merge_reque...

Ah, good to know.

Re: Ghostty 1.0

#135
post #26

I have found the following community site for generating Ghostty config quite helpful https://ghostty.zerebos.com/

This is great, thanks! It would be amazing if CMD + , would open this directly.

Re: Ghostty 1.0

#138

Ghostty has a hard-to-find "quake mode" that may interest some. During the beta I had it configured like this on macOS: keybind = global:cmd+space=toggle_quick_terminal quick-terminal-animation-duration = 0.1 There isn't an option to set the default height of the "quick terminal" window that I'm aware of but you can drag the bottom of the window after it opens and it will persist between toggles.

Does this work under Wayland? I remember that being an issue for Guake.

Re: Ghostty 1.0

#139
What am I missing? Can someone please explain what reason there is to switch/build a new terminal when we can use e.g. iTerm ?

Re: Ghostty 1.0

#140

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…

Just make sure not to get caught in the pitfall that is maximum render speed, which can lead to missing out on efficiency during slow and partial rendering. Missing damage tracking, always painting everything (even when the window is a full 4k monitor), etc. kills performance and input latency when dealing with realistic redraw workloads like text editing, blinking cursors and progress bars. Much too often to termina…

> 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”.

Post reply on HN