Hacker News
points by cassianoleal 2 days ago | 0 comments
I still don't understand the point of Ghostty, Kitty, Wezterm...

Konsole is way faster than any of those on my computer and it has all the usual suspects I'd expect from a modern terminal emulator.

The one feature I miss since moving to Linux and not having iTerm2 is tmux -CC integration. None of those offer it.

To be clear, I'm not attempting to be dismissive. I really want to understand what it is that they bring.

[–] sho_hn 2 days ago
KDE guy here.

Konsole is a fantastic and very mature terminal emulator, but it does have some real gaps that reveal its age.

The Qt toolkit that most KDE software is based on at some point introduced a next-gen toolkit-within-a-toolkit called Qt Quick, which most of our newer apps are written in. However, in its library form Konsole can only be embedded into apps that use the old gen toolkit. This is a real impediment to some efforts.

The old gen toolkit also typically doesn't use Vulkan or OpenGL for rendering (the new one supports both), and so Konsole's terminal renderer doesn't either. Konsole's real-world performance during use is arguably just fine, but it does leave a lot of performance and battery life on the table.

libghostty also has somewhat wider support for newer stuff like Kitty protocols, even though Konsole certainly trumps it in support for older stuff (like sixels).

There's some other shortcomings to Konsole that are not inherent to the technology, like accessibility support not quite being where it should be.

And while the default UI is, in most distros, OK, there sure is a lot of spiderwebs and spacebar heating lurking in the settings dialogs (of which there are strangely many). It's also a bit dated vs. our HIG at the moment.

Which is to say, these projects can and do have a point, especially if they provide a nice library instead of hoarding all the good to themselves.

[–] SomeHacker44 1 day ago
Thank you for Konsole. It is my daily driver and works well on KDE 6.8 for me. I use unlimited scrollback. It would be neat if it could have an unlimited scrollback that instead of using 15G RAM after a few weeks will dump it to disk and load on demand. And not hang if I hit C-S-F... I use it with tmux sometimes and agents.
[–] adityamwagh 1 day ago
Afaik, there’s an option for it in Konsole settings?
[–] reissbaker 2 days ago
A couple of annoyances I've had shipping CLI apps to Konsole users:

1. By default, Konsole disables OSC8 link support. Users can enable it manually, but you need to ship fallbacks by default since otherwise the default users will have a broken experience. Ghostty, Kitty, WezTerm, etc all ship working OSC8 support out of the box.

2. No built-in Nerd Font support, so if you want to render icons, you need to tell your users to set up a patched font or else have fallbacks. Ghostty and WezTerm ship built-in Nerd Font fallbacks if your configured font isn't patched.

That being said Konsole is much better than most emulators. iTerm2 is not bad, although it lacks Symbols for Legacy Computing Unicode support (which all of the above have, including Konsole, and which is very useful for drawing prettier terminal UIs). The worst by far is Apple Terminal, truly the IE6 of terminal emulators.

[–] cosmic_cheese 2 days ago
What's so bad about Apple Terminal? I've tried iTerm2 and others but never found a compelling reason to use them over the stock app. I don't live in the terminal like some do, though.
[–] reissbaker 2 days ago
Apple Terminal doesn't support:

1. The Kitty keyboard protocol, which makes it impossible to distinguish e.g. Shift-Enter from Enter

2. OSC8 hyperlinks

3. It breaks on APC queries, so you need special handling to not emit them

4. Symbols for Legacy Computing Unicode support

5. The Kitty Terminal Graphics Protocol (or sixel)

6. OSC 9 notifications (or any of the later versions)

and a bunch of other stuff, this is just off the top of my head. For a long time they didn't even support 24-bit color, although they fixed that in Tahoe.

It's totally fine for basic UNIX tooling, but pretty painful if you're trying to make nice interactive TUIs.

[–] nasretdinov 1 day ago
> It's totally fine for basic UNIX tooling, but pretty painful if you're trying to make nice interactive TUIs.

This sounds like a deliberate choice from Apple TBH because they, well, like their UIs and don't want to promote TUIs necessarily :)

[–] KetoManx64 13 hours ago
> You will play In the sandbox that we give you and you will like it and we will make it painful for you to go outside of that
[–] skydhash 2 days ago
> It's totally fine for basic UNIX tooling, but pretty painful if you're trying to make nice interactive TUIs.

The latter seems always to be about aesthetics, not about UX.

[–] filcuk 1 day ago
How is TUI not UX related? The entire point of it (for me) is to make CLI more user friendly
[–] hnlmorg 2 days ago
> By default, Konsole disables OSC8 link support.

That is, in my opinion, the correct default.

[–] adrian_b 2 days ago
I believe that the default behavior should be to never open a link without a confirmation from the user that this may be done.

This should be enough to avoid malicious links. I do not believe that completely disabling links is a good default, because they are very frequently useful when you read some text file in the terminal window.

[–] reissbaker 2 days ago
Yes, I agree. Ghostty et al don't open-on-click, but on hover they'll show you the URL and there's a keyboard shortcut + click to open. This is much better UX than disabling OSC8.
[–] tjoff 2 days ago
Yeah, because more complexity where you don't expect it doesn't cost anything?

Up until 5 hours ago this fix was not present:

> The displayed target is sanitized so invisible and line-breaking characters cannot conceal the effective destination.

https://github.com/ghostty-org/ghostty/security/advisories/G...

The sensible default is to have it turned off. And by the looks of it Ghostty versions before this you couldn't even turn it off.

[–] reissbaker 2 days ago
"One implementation of a feature had a bug, therefore this feature should be turned off on all implementations by default" is probably not going to convince people who think the feature is good.

If you don't want to be able to have clickable hyperlinks, by all means use Konsole — no one is forcing you to use Ghostty. But if you want to know why people like Ghostty's approach vs Konsole's, it's because Ghostty pushes terminal emulator features forward and is low latency. Konsole is low latency and adopts some but not all features that other people invent. It's a noticeable difference and so people who like the feature part of the former like Ghostty/WezTerm/Kitty more than Konsole. If you don't care or dislike that part, and want a more conservative terminal (that is also low latency), Konsole and many others further on the conservative spectrum exist.

[–] hnlmorg 2 days ago
It’s not just one implementation. Browsers have been struggling to get this right for decades and now we are destined to repeat all the same problems all over again with an entirely new syntax of inlined markup.
[–] tjoff 1 day ago
Bugs are fine, but this wasn't really a bug. It was lack of foresight.

I haven't used Konsole, but I do like this "recent" focus on terminals and have used many of the newer ones. Dailydrived st,alacritty,wezterm,ghostty,kitty,foot (probably forgot some) and I live for the regex pattern matching copy shortcuts etc.

I learned about OSC8 because my terminal (whichever it was) used one of its features and I didn't know it was possible to do that. My immediate thought was, how is the security?

And it is very disappointing to see how little effort people have spent on that. That is really one part that I expect more from modern incarnations of the old terminals where I can sort of forgive them for the lack of security posture.

I like ghostty, I really do. But this is not a good look, and to be clear it isn't just ghostty. Without looking for it I've stumbled upon several OSC8 and OSC52 bugs (in other software) recently.

[–] hnlmorg 2 days ago
I don’t want random text in my terminal to be a link. I do not find that useful.

If people want it enabled, they can enable it. It shouldn’t be the default.

[–] foltik 2 days ago
Surely you realize most people would disagree?
[–] hnlmorg 1 day ago
Most? Probably not

Someone? Almost certainly

[–] blackqueeriroh 2 days ago
Congratulations, don’t use Ghostty or terminals built on top of libghostty and you don’t have to!
[–] hnlmorg 1 day ago
I don’t. But the problem with OSC8 is it opens up whole new vectors for security vulnerabilities in an application that is, by intent, used for some of the most security sensitive work in our jobs.

I wouldn’t mind OSC8 so much if it had proper security auditing but it doesn’t. The whole thing was pushed by one guy on a GitHub gist who blocked anyone who dared discuss security issues.

At least with browsers, you have masses of people testing these things. But there’s no rigour to any of the tests that happen with terminal emulation. Let alone independent security audits.

And at this rate, it’ll only be a matter of time until we see “don’t cat untrusted READMEs” advice because they might contain boobytrapped escape codes. Which is an absurdly bad place to end up.

[–] Geezus_42 1 day ago
There's a million reasons why you shouldn't "cat untrusted READMEs".
[–] zetanor 1 day ago
I've always found emojis in the terminal distracting, so it's actually quite a relief to learn that Konsole is guarding me against a whole other class of glyphs and logos.
[–] throwaway2037 1 day ago

    > By default, Konsole disables OSC8 link support.
Is this for security reasons? I am sure the Konsole has a reason for it.
[–] tmtvl 15 hours ago
> if you want to render icons

...then you shouldn't be making a CLI app? I mean rendering and command line don't seem like they go well together.

[–] diath 2 days ago
1) Personal preferences: different terminals come with different defaults, some people do not want to tinker with the settings, so they just stick with whatever immediately clicks.

2) Technical curiosity: some people probably started their own terminal project just for the fuck of having made their own - and they eventually gained a userbase.

3) Feature set: Most terminals implement most features these days, but at the time these projects started, you'd have a feature matrix between features and terminals because most terminals lacked some features; so people would pick whatever suited their needs.

Personally I've been using kitty for years mostly due to 3), at the time I chose my forever terminal, I evaluated like 12 different ones, and kitty was the only one that covered most of my needs without feeling like it suffers from random quirks, and I like that it has built-in terminal multiplexer (a'la tmux) and emoji picker.

[–] sigbottle 2 days ago
The terminal ecosystem needs to change, and these terminals support a lot of cool features. Ghostty's pure reusable terminal state machine being a source of truth, Kitty graphics, Wezterm and its mux domains & lua config, lots of cool ideas there.

Having having an industry player like hashimoto's superlogical driving terminal features is the extreme version of that

[–] alsetmusic 2 days ago
> Ghostty's pure reusable terminal state machine being a source of truth

Can you please explain what this means? I have Ghostty installed just as a backup to use when I have terminal saturation in my default (MacOS Terminal). But other than being super responsive, I don’t know why people love it so. Perhaps I’m missing something large and compelling.

[–] B4uler5 2 days ago
I assume the quote is referring to libghostty. In which case a lot of different tools like vs code, Emacs, Gvim, Intellij and other IDEs, even web consoles on stuff like Azure essentially use and reimplement the same core, the idea behind libghostty is to replace those with a common component where long term development can better support the needs of all terminals.

In terms of ghostty itself its just a highly competent use of libghostty, Mitchell’s message above about it being a tech demo is tongue and cheek, but its not far off from the truth. It is just a really solid no bells and whistles, bar excellent execution, terminal emulator that uses libghostty.

[–] sigbottle 2 days ago
Terminal state machine parsing is a very tricky thing, especially when you have people defining arbitrary protocols to interact with it. So having one implementation simplifies the development a lot. Of course this buys you into their ecosystem and whatever ghostty specifically supports etc.

A lot of other terminal emulators can expose similar reusable things (alacritty comes to mind) but libghostty is the most well supported one

[–] alemanek 2 days ago
It being super responsive is the reason I switched to it. MacOS terminal had issues keeping up with Claude Code. It would frequently be super slow rendering the text output or sometimes just stop altogether.

When looking at options I looked at speed and simplicity. Ghostty fit the bill but I did evaluate iterm as well. Excellent terminal but too many features for what I was looking for. I live in the terminal but am not a Terminal App power user if that makes sense.

So, it really comes down to what you want and what your workflow looks like. Ghostty has been flawless for me the past 9months. It gets out of the way and just works really well.

[–] KerrAvon 2 days ago
Really? Claude Code is buggy but not very demanding in terms of rendering -- are you sure the perf issues were local?
[–] alemanek 2 days ago
I might not be using the correct terms. But, here is what I was seeing:

- in a running session text display would slow down intermittently. Like 2-3 words a second

- occasionally terminal would stop, some times in the middle of showing a response, and would need to restart the terminal to get it back. But I tailed the session logs and Claude code didn’t think anything was amiss. It was proceeding like normal

After switching to Ghostty these issues went away and has been rock solid since then.

EDIT: formatting

[–] PuercoPop 2 days ago
The issue the OP mentions was likely a known memory-leak in Ghostty that has since been fixed. Claude was triggering the bug in Ghostty but the bug was in Ghostty. Ghostty's author blogged about it

https://mitchellh.com/writing/ghostty-memory-leak-fix

[–] Geezus_42 1 day ago
The said MacOS terminal was slow, not Ghostty.
[–] epihelix 2 days ago
> The terminal ecosystem needs to change

What is your justification for this statement? Why does it need to change, and what does it need to change to? Personally, I've not felt this (and I spend a lot of time in the terminal). Fish shell and Byobu give me everything I've ever wanted.

Like the poster you were replying to, I don't understand what these new terminal emulators bring to the table, other than potentially more resource usage.

I feel that there's something here that I'm missing (ghostty is clearly popular, so it must bring something both new and useful to the table), but I'm genuinely not sure what that is.

[–] ChickeNES 2 days ago
Why would a terminal multiplexer need an entire company behind it? Especially since it looks identical to the many other vibe coded alternatives (including my own lol).
[–] ravenstine 2 days ago
There's always gonna be something that's better, faster, bigger, badder, stronger, thicker, firmer, etc., and terminals really aren't one of those things where I am interested in exhaustively testing all of them to find the truly greatest one. A terminal is also one of those things where if you find one that is perfectly adequate then there's little motivation to even bother using trying one. And there's the whole "devil you know" aspect. The only reason I rarely try a different terminal is if the stock terminal on whatever OS I'm using lacks some basic niceties that should be expected in the year 2026.

I like Ghostty because I find it both fast and configurable, and it's multi-platform without treating macOS like the red headed step child. I also appreciate how its configuration is text-based, which I prefer to someone's opinion of how a configuration GUI should behave, and I think it's good the developers aren't wasting a second of their time thinking about a configuration GUI.

[–] mixmastamyk 2 days ago
Funny, I won’t use a term emulator unless it has a good GUI config. Even SGI and Windows Command prompt had them in the 90s.

Also the konsole context menu and default toolbar are a mess.

[–] lucasoshiro 2 days ago
I also thought like that, but you only to set some defaults and you're ready to go. If you still prefer a GUI there are online generators. Nowdays you can also vibecode them, they are very simple and any LLM will do it right
[–] ChickeNES 2 days ago
If you have to see them, they aren’t defaults. It’s bad enough that Windows Terminal doesn’t expose its full configuration and forces you to edit the config by hand for more advanced stuff. Feels like a step backwards when something like iTerm 2 gives you access to all settings in a (admittedly kinda crappy) GUI. This also kinda begs the question why there’s not a /TUI/ configuration manager shipped…
[–] Geezus_42 1 day ago
Seriously, iTerm2's config GUI is so confusing and convoluted. I figured it out, but I always found it annoying trying to remember which menus to dig through to find that one setting I need.
[–] lucasoshiro 1 day ago
That's what I thought at first. But all the niceness of having a settings GUI didn't pay the unwanted bloat. My first try was to find a "debloated iTerm2", and then I found out that Ghostty's settings aren't the burden that I thought they would be
[–] mixmastamyk 2 days ago
There are mature emulators for decades now, why go backwards? I guess there are a few tiny features that might be useful, and am open to them. But a new project needs to be strictly better, not two steps forward, one step back.

Ghostty is getting there though, and today is a milestone, not complaining too loudly.

[–] Geezus_42 1 day ago
Because the old ones refuse to change or add New features. Which is fine, there are plenty of users who dislike chabge. However, it means you have to start a new project if you want to support most modern features.
[–] Analemma_ 2 days ago
The lack of a config GUI in ghostty used to bother me, but to be honest now I just describe to Claude what I want to change and it does it. It would still be nice to have one eventually but I can see the argument for deprioritizing it.
[–] adrian_b 2 days ago
I assume that this depends on your computer/GPU/GPU driver.

I have used Konsole for many years and I have used kitty for about 2 years in 2024/2025, then I have switched to ghostty around the beginning of 2026.

At least in my computers (with NVIDIA GPUs and Gentoo Linux), kitty was many times faster than Konsole and Ghostty even faster.

Moreover, in the now somewhat distant past when I was still using Konsole, it did not have some font rendering features that I desired, but that might have been solved meanwhile.

A reason why the terminal emulator speed is important for me is that I frequently compile big software projects and I find it unacceptable for a compilation to be slowed down by the low speed at which the compiler output is displayed on the terminal window, which happened frequently with all terminal emulators older than kitty and ghostty (I have always used CPUs with enough cores so that compilation itself is very fast, so the older terminal emulators become the bottleneck).

[–] throwaway2037 1 day ago
Real question: Is the Linux kernel terminal the fastest of all? If yes, why not compile there?
[–] adrian_b 1 day ago
Because I run in parallel other programs and I want to interact with their windows, which would be much too cumbersome if I needed to switch between a virtual console and the GUI desktop forth and back any time when I want to watch the compiler output.
[–] skydhash 1 day ago
> A reason why the terminal emulator speed is important for me is that I frequently compile big software projects and I find it unacceptable for a compilation to be slowed down by the low speed at which the compiler output is displayed on the terminal window

I’m strongly skeptical of this as pty are character devices and buffered. Programs and terminal are very loosely connected.

[–] adrian_b 1 day ago
Compiling any big software project produces far more text output than can be stored in any pty buffers.

There are a few big projects that redirect the compiler output and attempt to print only one line per output file, so when all goes well there is much less output text, but with those it is usually more difficult to debug failures.

[–] skydhash 1 day ago
> There are a few big projects that redirect the compiler output and attempt to print only one line per output file, so when all goes well there is much less output text, but with those it is usually more difficult to debug failures.

Why? If you use something like tee(1), you can get the full log in a file and then filter line according to what you want.

> Compiling any big software project produces far more text output than can be stored in any pty buffers.

The reason of my skepticism is that, according to your statement, reading a source file, then writing the compiled object file is way faster than a few printf through a kernel object in memory. Even for the terminal consuming the characters, parsing, and displaying the lines should not be a computation hog for most terminals

[–] lucasoshiro 2 days ago
For me: it doesn't really "bring" anything more than what I expect from a terminal.

In Mac, we had the default terminal app which has some problems with TUI apps and other small issues. iTerm2 is the replacement that most users use, but it become too bloated with useless features and AI, while it was hard to keep a good config file that I could share between devices. Ghostty was a sane mid-term for me: a good and modern terminal, with a simple config file, maintained by someone that I trust (Mitchell Hashimoto) and only that.

About Linux: I don't use Ghostty in Linux because I'm comfortable with Konsole.

[–] BorisMelnik 2 days ago
I know for many folks they like the fact that it is cross platform (works on mac/linux) etc and gpu acceleration which is really nice to have.
[–] xcrjm 2 days ago
Yeah, I recently tried out Kitty and Ghostty just feels much smoother when rendering most TUIs and even some more basic stuff like the homebrew progress bar. It is also better about respecting platform conventions for things like keybinds and window/tab behavior.
[–] kccqzy 2 days ago
I have been using Alacritty for its GPU acceleration long ago. Ghostty was slightly faster, but then Ptyxis was also faster. Since I preferred to configure my terminal with GUI, I have switched to Ptyxis.
[–] flohofwoe 2 days ago
For me it's simply that iTerm2 got really fat over the years, and Ghostty was a nice and slim alternative - plus it has one of the better Kitty Graphics Protocol implementations which is fun to tinker with. e.g.: https://github.com/floooh/chipz-kitty (needs zig-0.17.0).
[–] lioeters 2 days ago
> chipz-kitty: Emulators in terminal experiment.

Cool! How fun, I'm a big fan of your work and will enjoy learning from this project too. (:

[–] paride5745 2 days ago
I use Linux at home and Mac at work. I use Ghostty simply to have the same terminal on both systems.
[–] OnlineTux 2 days ago
Me too. I was using WezTerm for a while for the same reason.

It wasn’t the only reason I switched, but I prefer config to be config and code to be code rather than my WezTerm config to be executable.

[–] lioeters 2 days ago
Kitty is really nice, a programmable terminal that does everything I want, GPU rendering, etc. Haven't used Ghostty yet but one of its advantages is libghostty, modern terminal emulation as a library.

> libghostty: a cross-platform, minimal dependency library that exposes a C API so feature-rich, correct, and fast terminal functionality can be embedded by any application anywhere.

Oh the author actually posted about it just now in rich detail. It's pretty exciting for people who spend much of their time in the terminal.

[–] ada-h00k 2 days ago
For me, the main reason to use Ghostty is simply that mouse support works right out of the box. In Konsole clicking a spot to move the cursor only works if you're using Bash. While it also works with the Fish Shell on Ghostty.
[–] mtremsal 2 days ago
Same here. ghostty + fish = just works out of the box, no plugins or dotfiles needed. Plays well with accessing remote tmux claude/codex sessions as well.
[–] slowin 2 days ago
I don't think Konsole is actually faster than Kitty or Alacritty. Kitty is really nice and an innovator in a lot of terminal standards. It's also non-commercial and not related to any sort of startup (not that Konsole is either). It's definitely my first choice of the bunch, followed by Alacritty.
[–] arzig 2 days ago
Konsole seems to keep up with modern features as well. For instance I realized yesterday that it renders the newer progress codes that clis can emit. I am content.
[–] andai 2 days ago
I tried a bunch of terminals and ended up switching back to xfce-terminal, fastest I have tried by far. (It's just the default that ships with my distro.)

Actually I think xterm was even more performant, but the eye sore wasn't worth it for me.

[–] rnewme 1 day ago
Also in the xfce camp. KISS
[–] n6242 2 days ago
The other day I was able to click on Ghostty, then open Gnome Terminal, type a command and run it before Ghostty had finished loading.
[–] christophilus 2 days ago
Yeah. It's slow on Linux, for sure. I use Foot, which as far as I've tested is the fastest to launch. I use Niri and launch Foot terminals all the time as part of my workflow (it's just how my mind works), so time to launch matters to me.
[–] qudat 2 days ago
Monstar is a libghostty derivative that resembles foot: https://github.com/rockorager/monstar

Namely it is wayland only, cpu rendered, and doesn't have any window decorations

[–] Geezus_42 1 day ago
I really love Niri.
[–] koyote 2 days ago
Yep, same here but with xfce4-terminal.

I've just reverted back to using that as it's faster to load and has all the features I need.

[–] acedTrex 2 days ago
Konsole is not gpu accelerated and is several orders of magnitude slower as a result than those that you listed?

The acceleration is the primary point.

[–] hxugufjfjf 2 days ago
It works well, that’s my only requirement. I could ask you the same, what’s the point of Konsole, what value does it bring?
[–] cassianoleal 2 days ago
You could, but my answer would probably skew your opinion about as much as yours did mine. :D

To me the point of Konsole is that it works well, plus it's already there. Ghostty I need to make an effort to have it, however small it is, and I'm just trying to understand what I'd be missing if I didn't.

[–] hxugufjfjf 2 days ago
Konsole is not already there for me. I would have to make an effort to get Konsole, just like Ghostty. I’m struggling to see what point you are trying to make. Do you want someone to tell you Ghostty is better than Konsole to convince you to switch, or … not?
[–] OnlineTux 2 days ago
Cross-platform native GUI, built-in nerd font symbols. Simple text file configuration with trivially easy platform/machine-specific drop-ins.
[–] zeendo 2 days ago
Seems a bit of a disingenuous comment when you initially said "I still don't understand the point...".

Surely you understand Konsole is not already there for most people?

[–] skydhash 2 days ago
This days I don't really care about the terminal I use. It's xterm on OpenBSD, konsole on Fedora KDE, terminal.app on MacOS,... As long as I can use cli and the few TUI software I use.
[–] onehair 1 day ago
I have the same wezterm configuration on linux, macos and windows. that's the point of wezterm for me. I now use ghostty on Linux and macOS, cuz ghostty has more out of the box and is being up to date, and doesn't require me coding functionality xD small config file does all for me. when Windows support comes in, I will have one terminal emulator on all 3 platforms I am using
[–] whalesalad 1 day ago
Same. It is the only cross platform terminal emulator that truly provides an identical experience for me between Mac and Linux. Was really easy for me to get it to behave more or less just like iterm2 (cmd+1..9 for tabs) with Toshi on Linux. So my muscle memory works across macos and kde. Dotfiles: https://github.com/whalesalad/dotfiles/blob/master/wezterm/w...
[–] tetraodonpuffer 2 days ago
for terminals I personally am using kitty, but libghostty is great and powers ghostel in emacs which is amazing. Also note if you start trying to look at unicode correctness, in my experience ghostty is in general the best among all alternatives.
[–] pritambaral 2 days ago
> Konsole is way faster than any of those on my computer and it has all the usual suspects I'd expect from a modern terminal emulator.

Same boat here, though I also get to enjoy some of the benefits of libghostty, via ghostel in Emacs. Ghostel is noticeably faster when there's a lot of output being dumped, but I don't often need the speed and use it only because it's integrated rather well into the rest of my Emacs.

> tmux -CC integration

If you can stomach Emacs, there are at least two packages that implement this, one via eat and another via vterm, though none via ghostel just yet. Shouldn't be difficult to port, though.

[–] linsomniac 2 days ago
>I still don't understand the point of Ghostty, Kitty, Wezterm...

WezTerm can run on my Mac but give me a native GUI experience of a Wezterm session on my Linux workstation. It's like tmux, but with a native GUI experience including mouse click-drag selection that doesn't pick up "window" borders.

That alone is what is keeping me on Wezterm, since I get a native experience on some terminal sessions I access remotely on my macbook but then can switch to on my 30" screen when I'm at my desk.

[–] commandersaki 2 days ago
I don't know about the others as I used Terminal.app on mac since Panther, but Ghostty has been a pretty good upgrade, at first offering 24-bit colour which Terminal.app didn't have at the time of its release. I also like the shell integration such as easy selection of command output. I don't ask much from a terminal as evidenced by using Terminal.app for almost 2 decades, but Ghostty has not once been an issue and is 'invisible' to me.
[–] himata4113 2 days ago
vouch this comment since this is a pretty common question people have, I don't believe it should be dead.
[–] paaloeye 2 days ago
I do believe it should be dead
[–] jd3 2 days ago
iTerm2 feels overwhelming to me. I think the default Terminal.app is good enough.
[–] iberator 2 days ago
I was sceptical for decades as well. But they are amazing - no more closing the xterm by mistake. I'm using those because I wanted for example a single window with THREE consoles open at once AND being able to handle some ANSI crazy theming.

Xterm failed me :( Tabby just works.

[–] prinny_ 2 days ago
The advertised point is it needs zero config to work outside of the box. For example nerd fonts are included by default whereas you need to install them if you are using let’s say iterm2.
[–] bombcar 2 days ago
The point for me is each one can have ten or so claudes, so any one crashing doesn't take down all the claudes ... and I don't have to learn tmux.
[–] bradly 2 days ago
To add to the other good points made in sibling comments, MacOS has butchered fullscreen to the point where some of us depend on MacOS terminal emulators having the "non-native fullscreen" config option. Personally, Ghostty does the best job supporting my preferred terminal environment of non-native fullscreen with tabs that works with an auto-hiding menubar and the camera notch.
[–] hexasquid 2 days ago
Can konsole do the fancy shader and inline images? I think that's all that distinguishes the others but I may be overlooking things.
[–] cassianoleal 2 days ago
I have no idea what that is or why I would want it.
[–] the_mitsuhiko 2 days ago
I'm not sure why you want shaders, but if you use a coding agent in the terminal you definitely want image support. Otherwise it's very hard to see what the agent is seeing.
[–] novafunc 2 days ago
I can use Ghostty and use the same featureful terminal on Linux and macOS.

I also hate configuring Konsole, most KDE apps for that matter. Being able to have a plaintext configuration file I can keep in my dotfiles is way simpler.

[–] olejorgenb 2 days ago
I don't know Konsole, but kitty have tons of features other "plain" terminals lack. It's not just about speed (which I never got the obsession about either)
[–] seemaze 2 days ago
tmux control mode (-CC) is the killer feature I'm waiting to land in ghostty
[–] whalesalad 1 day ago
I find Konsole's rendering to be pretty bad. Wezterm is really good.
[–] paaloeye 2 days ago
Ghostty is so much better than iTerm2! Don't get me started...
[–] wpm 2 days ago
I'd love to, I switched back to iTerm after not really feeling any big difference in my uses cases, but also hating the crappy plain text with no defaults listed config that required me to use a goddamn web app to comfortably learn and fill out.

There was also some pretty noticeable differences in character rendering between the two with identical-as-I-could-make-them font settings.

[–] paaloeye 2 days ago
> here was also some pretty noticeable differences in character rendering between the two with identical-as-I-could-make-them font settings. I'm pretty sure it was iTerm's problem.

I've tested a number of Terminal Emulators on macOS and Ghostty's rendering is always superior.

You should give 1.4 a try.

[–] wpm 17 hours ago
How and why? How is Ghostty's text rendering better? And why should I go try 1.4? Did something change in how it renders text?

Straight up it doesn't look as good to my eye as the built in Terminal and iTerm with the identical text settings and theme, in so far as I can actually get Ghostty to pick up the right font style with its "fire some text into an file and hope its the right format"

[–] paaloeye 2 days ago
It just works. — Steve Jobs

Ref: https://arne.me/blog/we-need-more-zero-config-tools

[–] wpm 2 days ago
Yeah except when it doesn't. I shouldn't need to reference documentation to change my terminal font.
[–] paaloeye 2 days ago
Honestly, iTerm's settings were always a mess in my opinion.

I feel like good tools should be invisible and Ghostty's lack of fully fledged Settings app is a feature, not a bug.

Just open it in Kakoune/NeoVim and change with a speed of thoughts. Never used any third-party Settings apps though.

Ref: https://news.ycombinator.com/item?id=48858121

[–] wpm 2 days ago
Change with a speed of thought

Yeah, except the default config file doesn't EXIST and there is nothing but the reference docs to tell you what the hell you're supposed to put in there. What am I supposed to do, guess? Is it `font=` or `font-family` or `font-name`? That's fucking terrible. The very existence of a website like this: https://ghostty.zerebos.com proves the failure in my opinion.

Good tools should be invisible. Good tools behave the way I want them to. That's different than the way you want them to behave. Or appear. Good defaults are good. That is absolutely no excuse to abandon good UX for configurability.

I'm happy the defaults work for you. They don't for me.

And don't get me wrong, ghostty is a fine terminal and I don't begrudge it, and I think libghostty is awesome, it's just not the application for me.

[–] OnlineTux 2 days ago
What do you mean “there is nothing but the reference docs to tell you what” valid configuration options are? Where would you expect that to be documented otherwise?
[–] micromacrofoot 2 days ago
cute little mascots
[–] samsari 1 day ago
> I still don't understand the point of Ghostty, Kitty, Wezterm...

If you're genuinely not trying to be dismissive and just have a sincere question you want to have an answer to then I _strongly_ implore you to be more aware of and careful about how you express yourself.

Because as your first sentence is worded virtually all readers will assume you are hostile and not asking in good faith.

[–] oofbey 2 days ago
Lots of things bother me about my terminal emulators, and it's almost always in the category of "things don't work right". It's never "I wish my terminal emulator ran faster." Ghostty seems hyper focused on speed, with the negative side effect that compatibility breaks - in practice. I get that it's following all the newest standards or whatever it's doing, but in reality it always needs custom setup to work right. And for me the net effect is that it's always creating problems, not solving them.