Live data from Hacker News

Libghostty is coming

mitchellh.com

211–220 of 275 posts

Re: Libghostty is coming

#212
I love the idea, and I'm doing something similar in Ruby (which, yes, means it will be far less universal than a compiled library; that's an intentional tradeoff - I don't need it to be universal, and even less so when someone is willing to invest far more effort into something that is universal) inspired by AmigaOS, where a terminal window was easily accessible to any application whether it was started from the terminal or not, by opening a file handle to "CON:" (which meant e.g. scripts could also pipe this directly into a newly opened terminal window).

It's one of a few "lost capabilities" of AmigaOS I'm glad to see getting addressed. You can of course fix this today by using one of a variety of terminal widgets, but the ease of being able to just spin up a full terminal window from "anywhere" was very powerful for simple utilities etc.

Re: Libghostty is coming

#213
post #208

Earlier quoted context omitted.

Ghostty is his hobby project: why would he do that?

Because maintaining is not as fun as starting? Because other people can maintain a well structured project but not as many people can start something from scratch? Because his skills can be better used elsewhere?

That sounds like the Google philosophy though, where smart people come up with ideas and write the initial implementation (then get promoted) and other less smart people take over, and you end up with a mess that had great potential like Bazel?

Re: Libghostty is coming

#214

I really want to like Ghostty but: - Still no ⌘F for find. - No way (that I know of) to select previous output or specific string and copy with only keyboard shortcuts. - No ⌘. sending CTRL-C (muscle memory and being advertised as native to the Mac is what one would expect). - Fonts still don't render as nicely as in Terminal.app. I've fiddled with `font-thicken-strength` and it's close, but not quite. Probably impos…

A few other ugly quirks in Linux:

- It doesn’t respect the user’s configured fonts. - Clipboard support is inconsistent. - The GTK4 UI is quirky, and has silly slow animations in situations which don’t make sense.

The first two sound like more serious issues, and I’m surprised that others haven’t found them dealbreakers.

Re: Libghostty is coming

#215

I really want to like Ghostty but: - Still no ⌘F for find. - No way (that I know of) to select previous output or specific string and copy with only keyboard shortcuts. - No ⌘. sending CTRL-C (muscle memory and being advertised as native to the Mac is what one would expect). - Fonts still don't render as nicely as in Terminal.app. I've fiddled with `font-thicken-strength` and it's close, but not quite. Probably impos…

By the rollercoaster of points this post is experiencing, I may have expressed myself poorly. To be clear, the concept of a modern, cross-platform Terminal core with native GUI implementations for each major vendor is amazing and I'm very glad it exists. It's just not quite there yet for me and I don't know if it ever will be. But I'm very excited by it and hopeful.

It’s weird to me that they consider GTK a “native” implementation — GTK is a whole [opinionated] layer of abstraction on top of the native interfaces.

It’s native in the sense that it’s not Electron, or Java, but it’s still a layer of abstraction which introduces all sorts of quirks.

Re: Libghostty is coming

#216
post #208

Earlier quoted context omitted.

Ghostty is his hobby project: why would he do that?

Because maintaining is not as fun as starting? Because other people can maintain a well structured project but not as many people can start something from scratch? Because his skills can be better used elsewhere?

> Because maintaining is not as fun as starting?

The previous commentor is hoping he'll move on because maintaining isn't as fun as starting? Why do you think he can't decide that for himself?

Re: Libghostty is coming

#217
post #38

I use ghostty daily now. Switched recently. In macOS I can re-map now caps lock to be cmd and it works for cmd+c. Everything else is great, sensible defaults and what's not easily customizable. Gruvbox light theme looks great too. The fact it's written in Zig is awesome too, if you ever question if Zig is ready, ghostty is your answer to that. Not seeing myself going back. It's great experience. Tip: if you combine y…

Can you tell my why I should consider ghostty? (as a daily Terminal.app user)

Everyone telling you that it's fast because iTerm2 is slow. Terminal.app is already faster than iTerm2 and on par o very close to most other alternatives in terms of speed.

I also used Terminal until recently and don't use any of the advanced features alternatives provide. The main reason to switch from Terminal.app is truecolor support. The terminfo thing is annoying but I just setenv TERM in ssh config. Better split panes is nice. Configuration in a text file is a matter of taste, but documentation is good.

Re: Libghostty is coming

#218

I really want to like Ghostty but: - Still no ⌘F for find. - No way (that I know of) to select previous output or specific string and copy with only keyboard shortcuts. - No ⌘. sending CTRL-C (muscle memory and being advertised as native to the Mac is what one would expect). - Fonts still don't render as nicely as in Terminal.app. I've fiddled with `font-thicken-strength` and it's close, but not quite. Probably impos…

> - No ⌘. sending CTRL-C (muscle memory and being advertised as native to the Mac is what one would expect).

For what it's worth, that shortcut also doesn't work in the Jetbrains terminal, Alacritty, Kitty, and even iTerm2. The only terminal emulator I've tried so far where that works is the built-in Terminal.app.

Post reply on HN