Release v1.0.0 · ghostty-org/ghostty
github.com
v1.0.0
  • Guy DudemanEnglish
    23•5 months ago

    What are the differences between all of these terminals?

  • @atzanteol@sh.itjust.worksEnglish
    20•5 months ago

    It’s ridiculous how much time people are spending performance optimizing terminals.

    xterm on a 120MHz Pentium on X11 in the 90s performed “fine”.

    • @geneva_convenience@lemmy.ml
      4•5 months ago

      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.

    • @PetteriPano@lemmy.world
      3•5 months ago

      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… 👌

    • Atemu
      2•5 months ago

      The problem with xterm is that everything else about it sucks. The only other half-decent performer is mlterm which is decent but has its share of issues.

      This one feels quite snappy; better than foot.

      • @atzanteol@sh.itjust.worksEnglish
        2•5 months ago

        Hah! It’s funny I just fired it up again for the first time and I do see a bit of flicker in xterm when paging full-screened in vim… So maybe there is something to performance optimizing terminals. :-)

  • @MonkderVierte@lemmy.ml
    11•5 months ago

    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?

  • boredsquirrel
    11•5 months ago

    Looked at it, interesting, no package, installed cosmic-term instead

    Uses alacritty under the hood, with tabs and tiles!

      • @taiidan@slrpnk.net
        1•5 months ago

        I like Kitty Graphics. I like graphics in the terminal for two reasons:

        1. integration with MC (midnight commander) style directory browser to show previews of jpegs, pdfs, etc.
        2. w3m web browser. I like being able to use that super-light weight webrowser when working/coding to keep me focused.

        Reason (1.) works with Kitty. (2.) does not. (2.) is pretty esoteric so I think sixel will probably die out soon due to the user base?

    • @brax@sh.itjust.works
      2•5 months ago

      I get that Sixel is old AF but is there a new standard or is it just an open sea of fragmentation where everybody picks some branched attempt at doing the same thing and rolls with it instead?

  • @Zucca@sopuli.xyzEnglish
    6•5 months ago

    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?

      • @Zucca@sopuli.xyzEnglish
        1•5 months ago

        Hm. That’s good. I wonder if it could be compiled to use no toolkit, but only rely on server-side decos.

        Oh well. I’ll give it a try.

        EDIT: We’ll it, indeed, can be compiled without toolkit. Nice. Strangely it defaulted to US keyboard layout. While all other programs do respect my system keyboard layout setting.

    • @sga@lemmy.world
      3•5 months ago

      i dont have xwayland, and it worked (though i did not test enough(lack of interest))

  • @Euro@lemmy.mlNorsk bokmål
    2•5 months ago

    warning: this is a giant rant lol

    Before the rest of my comment, let me be clear, I think this terminal is good, and i have no problems with it. My problem is with the hype.

    I simply don’t understand the hype whatsoever. First of all, it’s not even faster than my current terminal. especially when running cat /dev/random for whatever reason

    For the test i ran this rust program i saw in a comment thread somewhere

    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;
    }
}

    compile with rustc to test yourself.

    running the binary with hyperfine, i get ~35ms on my current terminal (foot), and ~40ms on ghostty.

    The terminal window sizes about the same size, in fact, there were 3 extra lines in foot so it was technically handicapped.

    Next is the whole “native ui thing”, which sure, if you use gnome, or mac is fine i guess, but what about kde where qt is used. And for me i simply hate title bars so i turned it off immediately and now it looks better.

    I do think the tabs are cool, not much to say about that, I wouldn’t use them, but for those who do, pretty cool.

    I have a similar opinion with the panes, personally i think if you want panes, just use a tiling window manager, or tmux or something, but i also dont really have a problem with this (tmux can be annoying).

    If I’ve missed anything let me know, because I really dont get it.

  • @w3dd1e@lemm.ee
    2•5 months ago

    But does it roll down like Yakuake did before I updated Fedora and broke it? :( That’s all I want.