Live data from Hacker News

Ghostty 1.0

ghostty.org

421–430 of 719 posts

Re: Ghostty 1.0

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

why don't you just pipe it into a file and then less it? if your redis stuff prints so much stuff you might want to reevaluate the respective program logic.

Telling to creator of Redis that they might want to reevaluate their respective program logic (Redis) is pretty funny, only on HN :)

Re: Ghostty 1.0

#423
post #392

Earlier quoted context omitted.

I uninstalled the app when I saw that Cmd+, opens an empty text file called config. I'm not going to learn more configuration languages or type 30 characters (or paste them from the browser) to toggle a binary setting.

Aren't plaintext configuration files standard? It's how I configure most applications (and how I like it, because it makes the configuration shareable). As a DSL, it's key-value pairs. It doesn't get much simpler than that.

It's a desktop/GUI application. It's definitely not a standard for those, no. I share the OPs frustation that I don't even know what I can configure and have to search web to be able to change something. And while the documentation is nice, it's not exactly great for this.

Also, having an explorable and searchable UI doesn't mean it's not saved in the same shareable and readable file.

Re: Ghostty 1.0

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

why don't you just pipe it into a file and then less it? if your redis stuff prints so much stuff you might want to reevaluate the respective program logic.

Sure, I redirect when there is to redirect, but sometimes during debugging you want to spam yourself to see what is happening during some stress testing when some code path is full of printfs. Also sometimes I'm just on the redis-cli and to test the system at scale I directly ask (like yesterday) for half million of similar vectors. It is very convenient I can type this on the CLI and see the result immediately, instead of flooding myself for seconds or minutes.

Re: Ghostty 1.0

#425

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…

Looks great. Switching from wezterm and kitty before that, and the native feel on macOS is indeed better than those emulated tabs. Also it is really quite zero config where to me it seems only one line of color theme is needed, together with setting TERM for ssh. (Default font happens to be mine.) Bundling so much color theme felt a bit waste of space, but it is nice that I don’t need to define them myself which also…

Use the browser's search on the page?

Re: Ghostty 1.0

#426

Earlier quoted context omitted.

why don't you just pipe it into a file and then less it? if your redis stuff prints so much stuff you might want to reevaluate the respective program logic.

Telling to creator of Redis that they might want to reevaluate their respective program logic (Redis) is pretty funny, only on HN :)

Haha, the question makes sense per se but there are definitely times where you want to see the output in real time. I'm a big fan of printf-debugging :D

Re: Ghostty 1.0

#427

Earlier quoted context omitted.

Thanks for this post, first thing I did was search "bitmap" in the thread. If I can't use Terminus (+Unifont fallback), it's not for me.

Curious as to how much it matters; if a TTF font looks similar and is fast?

> if a TTF font looks similar

It doesn't, especially on average DPI monitors. Oh, you mean the OTF trick.

Re: Ghostty 1.0

#428
post #106

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…

Alacritty on macOS and Linux user here (Windows Terminal on Windows due to easily different shells available, formerly used iTerm2 on macOS). I make up for lack of tabs with zellij locally (tmux remotely). Also allows me to relog or close/update Alacritty. I will give Ghostty a whirl but why no shout out to Alacritty? Which features am I missing out on?

Ghostty's community is much nicer compared to Alacritty :)

Re: Ghostty 1.0

#429
post #384

Earlier quoted context omitted.

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…

> Missing damage tracking, always painting everything (even when the window is a full 4k monitor), Out of curiosity, what GPU accelerated terminal does this.

+1, no idea.

But maybe to add a little bit of context, "damage tracking" means for example, that if there is any ongoing animation (like a spinner), then only a small part of the screen will be re-rendered (with proper vertex-time scissors, so only relevant pixels will be computed). I am not sure if it makes sense in the context of a terminal emulator, but it's certainly a big issue for any non-toy GUI toolkits.

GPUs are incredibly fast parallel computers, so you will likely not observe any perf difference (unless you need order-dependent transparency which you don't), but it might improve your battery life significantly.

Re: Ghostty 1.0

#430

Earlier quoted context omitted.

I've been a beta tester from very early on. I came for the performance but stayed for the stability. I've only had a rare few crashes and all but one was a duplicate in the bug tracker. I thought I needed search but as Mitchell put it, not a 1.0 feature. Ripgrep was always the answer. Very happy to share the ghostty experience with the world!

Search was the first thing I noticed it was lacking. I hope it can be added at some point, sometimes you can't just run a command again to grep it.

Mitchell said it is planned in a recent interview on the Changelog podcast[1], just not in time for 1.0.

[1]: https://changelog.com/podcast/622

Post reply on HN