Gregory Anders

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

Performance of course but native is a big part of ghostty’s appeal; there’s an article by a neovim dev that expands on that native part a bit - https://gpanders.com/blog/ghostty-is-native-so-what/

This is a neat blog post explaining part of the magic: https://gpanders.com/blog/ghostty-is-native-so-what/

Ghostty is cross-platform, but it feels extra nice on macOS. https://gpanders.com/blog/ghostty-is-native-so-what/

See Neovim v0.10 changelog for how they use hyperlinks/OSC 8: https://gpanders.com/blog/whats-new-in-neovim-0.10/#hyperlinks

Pandoc can also do this: https://gpanders.com/blog/write-your-own-man-pages/

What is app detection? Regarding poor key binding support, I think that's not really a problem in modern applications. Quoting https://gpanders.com/blog/state-of-the-terminal/ : > Sending key presses as escape sequences requires that terminal applications are able to recognize and parse those sequences, so it is not something that “just works” out of the box. However, the kitty keyboard protocol has been widely adopted by both modern terminal emulators and terminal applications. Terminals which support the kitty keyboard protocol (to some degree) include Wezterm, Alacritty, kitty, foot, Ghostty, and iTerm2. Applications which support the kitty keyboard protocol (to some degree) include Vim, Neovim, Helix, kakoune, and nushell. This means that when using one of these applications in one of these terminals, all of the key encoding problems discussed above (as well as some others which were not discussed…) are solved. At least I indeed saw no such issue using helix in wezterm for example.