Cool project and... no screenshots? 😭
Every. Damn. Time.
post
What are the differences between all of these terminals?
If you're occasionally using them, there aren't any.
If you're excessively using them, there are many.
Could you highlight a couple, I'm kinda in between with my terminal usage....
Sure, I can do that.
- If you're looking for something lightweight, go for
storurxvt. These are Xorg-only. - If you want to configure it via GUI,
xfce4-terminalis the middle ground for lightweight and feature-rich. If you are on KDE,konsolewould suffice. You can use these on Xorg and Wayland. - If you want to work with multiple panes in a single window,
terminatoris your friend. Used this on Xorg but not sure about its Wayland compatibility. - If you want GPU acceleration and more features,
kittyandalacrittyis out there. Both should work on Xorg and Wayland. - If you want something like st but pure Wayland,
footis the best lightweight terminal emulator. My current personal favourite.
Fucking legend!
Pretty sure I'm using konsole right now, whatever it is, it came pre-installed on my distro.
Might check out foot and kitty, what I'm using is working right now, but always nice to look into different options.
It's ridiculous how much time people are spending performance optimizing terminals.
xterm on a 120MHz Pentium on X11 in the 90s performed "fine".
Assuming you had a pretty decent monitor and graphics output in the 90s, it may have been 800x600, but more likely 640x480, and you'd have been using the standard issue bitmap font with no anti-aliasing, blitted to screen using software rendering. Probably in a single colour, too.
Alas, the problem with that is that it doesn't scale. On xterm a 4K monitor, I can watch Vim redrawing the screen, paging through logs is painful. Use Kitty for the same, it's instant, I can flip through tabs and split screens too, and have niceties like anti-aliased fonts and transparency if I want them.
Some people spend a lot of time in the terminal, so I can't fault them for taking the time to make a nice working environment and sharing that work with others.
"decent" hardware back then ran at 1024x768. I never ran less. And definitely multiple colors. But sure - no anti-aliasing and other features. But also on hardware several orders of magnitude slower.
Though granted I don't have a 4k monitor so maybe there are issues with that...
Some people spend a lot of time in the terminal, so I can’t fault them for taking the time to make a nice working environment and sharing that work with others.
I mean - it's the first thing I open... Which is why I'm surprised others seem to have "performance issues" since I've never seen any.
Sure, it performed "fine".
But it was sluggish compared to the VGA ttys we were used to.
Now, if we can have something as snappy and at the same time as pretty as Eterm.. 👌
Every Linux user has the earliest and lowest specced version of the 4k Lenovo thinkpad from back when 4k on a laptop was impractical and a stupid idea.
The "Abandon all hope, ye who enter here" terminal?
Edit: that was once a comment in the sourcecode.
Hacker news users seem happy with its performance, so will try tomorrow. Fun with new terminals.
Looked at it, interesting, no package, installed cosmic-term instead
Uses alacritty under the hood, with tabs and tiles!
Looking at ghostty-git in AUR, zig is built on haskell? With 221 haskell libraries.
And what does it need pandoc-cli and hslua-cli for?
Checked the build.zig file for ghostty, seems to be for manpage generation. Zig itself doesn't use Haskell though
What the hell?
It’s awesome to see a project written with Zig!
For those that are, for some reason, incredulous of having more performant software (???), here's a simple program to demonstrate the point:
use std::{
fs::File,
io::{BufWriter, Write},
};
fn main() {
let buf = File::create("/dev/stdout").unwrap();
let mut w = BufWriter::new(buf);
let mut i = 0;
while i <= 100000 {
writeln!(&mut w, "{}", i).unwrap();
i += 1;
}
}
It simply prints the numbers 0-100000 to the screen. Compile it (rustc path-to-file). Run it in a non-accelerated terminal with time ./path-to-bin. Now time that same binary in a terminal emulator with GPU-acceleration.
The difference becomes more apparent with more text. Now, imagine needing to use something like find on a large set of files. Doing this on a non-accelerated terminal is literally slower.
It's fine if you don't need a GPU-accelerated terminal, but having acceleration is genuinely useful and a noticeable quality-of-life improvement if you do anything more than just basic CLI usage.
Isn't the terminal only going to affect performance when it's displayed in stdout? I'd think a program like find / using pipes would send the data under the hood and all that the terminal would deal with would be the output of the entire command.
Thought out choice but disappointing nevertheless:
My stance for now is that Ghostty will not support sixels.
What do you think about the Kitty Graphics Protocol?
Hm... I don't see it stating anything about wayland, but since it says "native" in some many places, I need to assume it won't use Xwayland, unless specifically told to.
Right? Anyone to confirm?
It works natively on Wayland. The UI uses gtk4.
i dont have xwayland, and it worked (though i did not test enough(lack of interest))
rn Im using Kitty, I'll check out Ghostty later.
I <3 kitty, will probably give this a look but I've got kitty so well tuned to my liking at this point it's hard for me to imagine switching
I've been a foot user for quite some time now.
However, this seems interesting.
top 50 comments