wezterm VS kitty

-- https://github.com/wez/wezterm/issues/3299#issuecomment-2145712082 wezterm.on("gui-startup", function(cmd) local active = wezterm.gui.screens().active local tab, pane, window = wezterm.mux.spawn_window(cmd or {}) window:gui_window():set_position(active.x, active.y) window:gui_window():set_inner_size(active.width, active.height) end)

I tried WezTerm recently but I unfortunately could not type backslashes on an ISO keyboard. There were other minor annoyances such as new tabs always opening on the last directory I was at and not my home directory (this was something that could be configured, but I never managed to do it). Ultimately, it was the problem with the backslashes that drove me back to iTerm.

https://github.com/wez/wezterm/issues/4051

It is just fuzzy from zooming up screenshots, a by product of the subpixel aliasing.

If it doesn't, you could probably add a post processing filter to https://github.com/wez/wezterm or https://github.com/alacritty/alacritty

O emulador de terminal que uso, WezTerm

wezterm (Linux, Macos & Windows)

A month ago, I came across WezTerm, a new GPU-accelerated, cross-platform terminal emulator written in Rust (and I’m not a Rust fanboy, for real!). It piqued my interest, so I decided to give it a try.

Kitty: https://sw.kovidgoyal.net/kitty

Initially, I used the Mac's built-in Terminal, but encountered issues with font loading. This led me to explore alternative terminal options. I initially chose Kitty, but after the official release of Ghostty, I made the switch. It has been running flawlessly for me.

kitty

I quite liked Kitty, and wanted to keep using it. But the slow startup was a deal breaker for me. Even with `--single-instance` it was at least 5x that of st for me, which is noticeable for an app I use very frequently. Besides, I'm not a fan of running a single instance of any app, since if (when) it crashes, all my work is gone.

Then I had a look around their issue tracker, and noticed others complained about this too[1]. And the dismissive and defensive response from the author just rubbed me the wrong way.

[1]: https://github.com/kovidgoyal/kitty/issues/330

kitty is very close, which is impressive when you remember that the vast majority of the work is done by one guy (Kovid Goyal).

https://github.com/kovidgoyal/kitty/issues — 0.239% vs 0.137%

https://github.com/kovidgoyal/kitty/issues — 0.729% vs 0.317%

https://github.com/kovidgoyal/kitty/graphs/contributors

In recent years, new terminal emulators have appeared. I tried using them mainly for testing macmon. A couple of years ago, I tried switching to kitty, which was faster due to GPU acceleration. However, it required too much customization and still looked very non-native for macOS. GPU acceleration was added to iTerm as well, so I stayed with it.

No it's not. The author smuggles opt-out telemetry and is suspiciously abrasive towards users pointing this out.

https://github.com/kovidgoyal/kitty/pull/3544

It's not just Kitty graphics, the Kitty Keyboard Protocol is a DOS waiting to happen, and Goyal with his customary charm is very hostile to the idea of correcting his mistake: https://github.com/kovidgoyal/kitty/issues/7749

This isn't the only problem with KKB, it must be deprecated and replaced.