• TimeSquirrel@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    Libraries and APIs are a moving target. Eventually it won’t run on modern systems anymore without modification.

    • john89@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      7 months ago

      Yeah, but if it hasn’t reached that point then is it really dead?

      Edit: Instead of downvoting me, consider this. What if the only update this program receives in years is one to make sure its still compatible with the libraries and APIs you refer to? Would that make it alive, or dead?

      It seems like you guys are advocating for updating just for the sake of updating, also bandwagoning a bit.

      • Yozul@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        Neofetch is literally a bash script. There aren’t any libraries or APIs it depends on, and there is basically no chance of it not working in the future. Some people just like to try and sound smart.

        The actual problem with Neofetch is that it’s not being updated with new ASCII art for new distros, and not adding new options to show things like a line for display server or other things some people might be interested in. It’s just getting out of date in regular boring ways.

              • Yozul@beehaw.org
                link
                fedilink
                arrow-up
                0
                ·
                7 months ago

                Uh huh. You think that some cloud computing processor just randomly can’t run a bash script? What, does the uname command not work on their processors or something? That would cause problems a lot worse than just Neofetch not working. I obviously don’t have one laying around to check, but I find that highly unlikely.