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

  • d3Xt3r@lemmy.nzM
    64·
    7 months ago

    Yes, it’s been long abandoned - no updates in over 3 years. Anyways, this is why alternatives like hyfetch, fastfetch (and others) exist.

  • eos300v@slrpnk.net
    342·
    7 months ago

    What’s wrong with no updates in 3 years? In my eyes, the software still does what it says in the box, meaning it is finished software. Games on the SNES are finished and haven’t had updates in 20+ years, I feel like software should be the same

    • gun@lemmy.ml
      17·
      7 months ago

      There are some things that do change. In my case, it says my window manager is sway when it is actually river. So certain things will stop working as expected if it is not maintained. This is different from a game, because as systems change, it doesn’t affect how the game works if the platform it runs on can be emulated. In a sense, the game is still being updated because the emulators required to use it are being updated.

  • umbrella@lemmy.ml
    311·
    7 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

    • teawrecks@sopuli.xyz
      151·
      7 months ago

      On the flip side, some packages just do something incredibly simple like print some info about your machine along with an ASCII image, and there’s not really anything else to do once it’s feature complete.

      • Sina@beehaw.org
        2·
        7 months ago

        Neofetch would need maintenance, because it cannot deal with new WMs and DEs that came out after abandonment.

        Just use Fastfetc…

        • teawrecks@sopuli.xyz
          1·
          7 months ago

          I actually did switch to fastfetch yesterday, but is it not just reading a string somewhere? Why would a new WM/DE break a glorified println?

          • Sina@beehaw.org
            2·
            7 months ago

            That’s not how it works. Otherwise it would correctly identify Hyprland, Labwc etc, but it tends to just print Sway for all WLR based.

            • teawrecks@sopuli.xyz
              1·
              7 months ago

              Interesting. Do you know where it gets “sway”? Or is it just assuming Wayland implies sway, because at the time it kinda did?

  • UnRelatedBurner@sh.itjust.works
    15·
    7 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.

  • femboy_bird@lemmy.blahaj.zoneEnglish
    161·
    7 months ago

    Yes long ago, I use hyfetch now (although neofetch has been argued by some to be completed meaning never needing any more updates)

    • exu@feditown.comEnglish
      141·
      7 months ago

      I’d argue against Neofetch being completed. PRs to properly handle custom colors in the terminal properly for example have been open for years.

  • thingsiplay@beehaw.org
    12·
    7 months ago

    I switched to fastfetch because neofetch was abandoned as far as I know. Or it might be that development just slowed down. Also fastfetch is faster than neofetch, even if its only very slightly faster, its noticeable (and I personally find neofetch annoyingly slow). And as one can see in the comparison image from you, fastfetch provides more info by default.

    Also the developers react and implement bug fixes or other features quickly (7 open, 403 closed issues): https://github.com/fastfetch-cli/fastfetch

  • flashgnash@lemm.ee
    6·
    7 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·
    7 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
        4·
        7 months ago

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

          • kixik@lemmy.ml
            4·
            7 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 !