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.
deleted by creator
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.
deleted by creator
That’s kind of exactly what I was thinking.
Thanks for the clarification.
deleted by creator
deleted by creator
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
deleted by creator
I think it’s on ampere iirc
Now fastfetch is my new friend
Neofetch is only dead if y’all let it die. Same as Hexchat.
number 4 will shock you!!1
Wasn’t screenfetch the thing neofetch was supposed to replace? Apparently it has more recent development activity (5 months ago), anyway…
I had no idea ppl actually cared about any fetches, not like it stopped working though. Just a guess but it’ll work for a good while, because it’s a damn fetch script:D
I’ve been using a custom version of paleofetch for NixOS for a while, but I decided to write my own clone of neofetch in Rust when I heard about the archival just for fun.
It has (or I suppose will have) parity with everything neofetch can output, supports dynamic plugins, is super fast bc compiled, and looks up information using asynchronous fetches. It’s configurable via a config file (JSON) to choose what you want to show (I think this is better than using CLI options for this kind of app).
I have the app’s framework/architecture up and running, I just need to finish implementing the rest of the data lookup and add more distro logos.
Once I get the data lookup feature complete, I’ll make the repo public so people can add their distros’ logos and use it, but I’m treating this as more of a pet project, so I doubt people will be that interested in using/contributing since plenty of other fetch programs exist, so I don’t care if it lives or dies; it’s just fun to make things :)
Tenatively named
fetch-rs, but I’m sure something like that already exists.
