Hello, tone-policing genocide-defender and/or carnist 👋

Instead of being mad about words, maybe you should think about why the words bother you more than the injustice they describe.

Have a day!

  • 0 Posts
  • 94 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle




  • It’s just an easy thing to contrast against.

    Electron is one of the slowest, clunky, memory-hogging ways to have a UI, and TUIs are the exact opposite. I don’t care if (name of company that ships Electron slop here) can ship your software webpage masquerading as software to more systems more easily. If your messaging “app” has input lag when I type something, it’s a dogshit experience.

    Of course, there are ways to ship GUIs that aren’t all of the things wrong with Electron, but comparing TUIs with those is less interesting and more a question of if the person likes to live in their terminal or not.





  • I would like to voice my support for the “no authoritarian” rule. Just because liberals use the term “tankie” to wrongly describe non-auth leftists, doesnt mean the word isn’t clearly defined or that it shouldnt be used.

    If you’re auth-“left” or find yourself doing apologia for the few genocides and instances of human rights voilations that the west opposes, you’re a tankie. It’s safe to say that genocide apologia and human rights violations of any kind should have no place on 196.










  • trevor@lemmy.blahaj.zonetoLinux@lemmy.mlGhostty terminal is out!
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Perhaps that’s true. Although, I think that should be tested because I’m a little unsure since pipes are just the stdout of one command being used as the stdin of the following command. There’s still some output, even if you don’t see it.

    In any case, find has many uses, many of which will print data to the screen, and find is far from the only use case in which this would be apparent. There are tons of situations in which you’re going to have to work with large amounts of stdout/stderr, and having a GPU-accelerated terminal will be much faster in all of those situations.


  • trevor@lemmy.blahaj.zonetoLinux@lemmy.mlGhostty terminal is out!
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 month ago

    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.