Why are everyone suddenly aware that Neochat is unmaintained. I mean, the last commit was 3 years ago and the last release alsmost 4 years ago. Just because the git repository got archived on a date does not mean that it was maintained up to that point.
Most people aren’t going around checking the commit history on every piece of software they use. The git repository being archived made the Linux news rounds, so now a bunch of people are newly aware. It’s not complicated.
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.
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.
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.
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…
Why are everyone suddenly aware that Neochat is unmaintained. I mean, the last commit was 3 years ago and the last release alsmost 4 years ago. Just because the git repository got archived on a date does not mean that it was maintained up to that point.
Most people aren’t going around checking the commit history on every piece of software they use. The git repository being archived made the Linux news rounds, so now a bunch of people are newly aware. It’s not complicated.
How does that make it dead?
Do they just need to update it for the sake of updating it?
Libraries and APIs are a moving target. Eventually it won’t run on modern systems anymore without modification.
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.
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.
That’s kind of exactly what I was thinking.
Thanks for the clarification.
deleted by creator
It totally does work though? Why would you say that?
Because I saw it in a thread when archiving was announced, and didn’t fact check like a dumbass.
Apparently it doesn’t work right on ARM systems or something
I have a Raspberry Pi. It works just fine.
I think it’s on ampere iirc
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.
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…