• john89@lemmy.ca
    link
    fedilink
    arrow-up
    8
    arrow-down
    5
    ·
    6 months ago

    How does that make it dead?

    Do they just need to update it for the sake of updating it?

    • TimeSquirrel@kbin.social
      link
      fedilink
      arrow-up
      24
      arrow-down
      1
      ·
      6 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
        8
        arrow-down
        7
        ·
        edit-2
        6 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
          11
          ·
          6 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.

    • Static_Rocket@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      6 months ago

      I don’t get people being worried about an offline application designed to run one shot as the current user not receiving updates. I do get maintainers dropping the package from package repos now that it is officially archived though…