Skip to main content ↑ ↓
Topic: Neofetch Situation in Late 2024 (Read 385 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Neofetch Situation in Late 2024

Not to revive an old post/thread, but it seems that neofetch is no longer maintained. Are there any official plans to remove/replace it at this time? Just curious.

I've been using fastfetch personally.

Re: Neofetch Situation in Late 2024

Reply #1 –
hi,
yes, the neofetch repo was archived in april 2024 :
https://github.com/dylanaraps/neofetch

so indeed, time to move to fastfetch (which is really fast, by the way :) )

Re: Neofetch Situation in Late 2024

Reply #4 –
Quote from: Ogis – on
Quote from: Sulfide9842 – on

Why not just leave it in the repo as it is? It just works.

Because neofetch is bloated, like fastfetch. I have recommended and will recommend to everyone a simple program written in the rust programming language. This is pfetch-rs

https://github.com/Gobidev/pfetch-rs

"Simple program" and written in Rust is an oxymoron.
Anyways these programs are pointless, just do uname -a if you want to tell the world you're running Artix for some reason.
And if you care about "bloat" simply don't install it, or even better, again, just use uname.

Re: Neofetch Situation in Late 2024

Reply #6 –
Quote from: Sulfide9842 – on
Quote from: TopHatProductions115 – on
Are there any official plans to remove/replace it at this time?
Why not just leave it in the repo as it is? It just works.

Not trying to remove it from the repos, just from the base installation. If it's no longer maintained, there's always a chance that the info it shows will be incorrect. I've already encountered it myself, sadly. It somehow got package count wrong on my VM. Also doesn't have to be replaced necessarily, though I would prefer fastfetch if I had to pick one.
 

Re: Neofetch Situation in Late 2024

Reply #7 –
It will be removed eventually, but it's not a critical to system stability package.