Ive noticed its has been any activity in their github for a longtime. https://github.com/dylanaraps/neofetch

There are a few more info that could be added nowadays like Display Protocol (Wayland/X11) and Display size. FastFetch does this but Neofetch is globally recognized.

Fastfetch vs Neofetch

  • umbrella@lemmy.ml
    151·
    8 months ago

    i hate always having to find out years later some software i use has been unmantained for years.

    there should at least be some sort of notification when this happens baked in to package managers

  • UnRelatedBurner@sh.itjust.works
    13·
    8 months ago

    it could display more info, but it doesn’t need to. And as far as projects go, if you don’t want a full diag, or have an ARM cpu (as someone else said), I’d argue it’s done. You don’t need to change a finished program.

  • flashgnash@lemm.ee
    5·
    8 months ago

    I’ve heard fastfetch is a lot better but I tend to have neofetch installed anyway because it’s the known one

  • kixik@lemmy.ml
    3·
    8 months ago

    But neofetch tells you if wayland already:

    WM: Wayfire (Wayland)

    Actually while neofetch detects pretty well I’m using alacritty:

    Terminal: alacritty

    Probably they learned $TERM is really meaningless if using screen or tmux, but fastfetch totally misses this and mistakenly shows screen as the terminal:

    Terminal: screen

    The only thing I like of fastfetch over neofetch is that it’s faster, :) And yes the display missing, but I’ve never considered that something of much interest for such output… To me neofetch is just fine, and on terminal it gives you a more accurate answer… In the end is a matter of taste… But what it does is well done, :)

      • kixik@lemmy.ml
        2·
        8 months ago

        No, screen is a terminal multiplexer, like tmux. The terminal emulator I use is alacritty.

          • kixik@lemmy.ml
            2·
            8 months ago

            They don’t run by themselves, they need a terminal emulator, or a console, underneath, so they can work. You can actually call screen on a console without graphical environment, and it’ll provide the console all benefits of multiplexing. That doesn’t make the multiplexer a terminal emulator by itself.

            So, in my mind no, screen is not a terminal emulator, alacritty is, like xterm is, and so on. The multiplexor just adds extra capabilities to the terminal emulator.

            At any rate, it’s not worth going any further. What I meant is that neofetch was able to find out and show I’m using alacritty, whereas fastfetch doesn’t show alacritty. And we can argue about the virtue of one or the other, but it’ll boil down to taste. I prefer how neofetch shows alacritty, hehe. Some might prefer fastfetch showing screen. And most importantly, this is not critical at all.

            There’s an issue on fastfetch filed about it, and one of the devs indicated when using the screen multiplexer, they could find out the terminal emulator underneath, however they couldn’t do the same with tmux. And to be consistent among multiplexers, they decided not to expose the terminal emulator underneath when using multiplexers, just show the multiplexer. I don’t agree with that argument, but it’s the dev right to choose to do that.

            Greetings !

  • kabi@lemm.ee
    1·
    8 months ago

    There’s a million alternatives that do the exact same thing. Fastfetch is just better, since it’s still maintained, and not painfully slow. I used to think neofetch being slow was kind of cute. Then I switched to fastfetch, and now I can’t bear the years neofetch takes to run.