[schmuelio]

I haven't used a considerable amount of time using st (I think for a total of 2 days on a VM?) I liked st just fine but I found the day-to-day performance of kitty really solid.

It feels like kitty takes _slightly_ longer to start up but it's still a tiny amount of time.

There's also the different configuration options, kitty has a config file but st (if memory serves) needs to be recompiled for changes.

I've found that initially kitty can have trouble rendering fonts with correct spacing but that takes a couple of minutes to tweak to your liking. And I think the colour configurations are a little more complex? I haven't had to change the config for a while though.

The GPU acceleration does make stdout much faster if it's unbuffered (in my experience) and on a 144hz monitor it looks so much smoother.

Hopefully that's enough of a comparison? Sorry I couldn't give more feedback, as mentioned I've only used st for a short time.

[alpaca128]

> It feels like kitty takes _slightly_ longer to start up but it's still a tiny amount of time.

For me the difference was large enough to switch to st. Kitty's startup takes 5-10 times as long and it's very noticable for me. As I use terminals a lot this meant a delay every time I opened an instance.

But this is a subjective thing of course. I have all the features I need with st and use a terminal multiplexer for the rest.

[michaelmrose]

You can also use kitty -1 to use a single instance of kitty although the startup time is already so small I doubt you could tell the difference without measuring