- cross-posted to:
- opensource@lemmy.ml
- cross-posted to:
- opensource@lemmy.ml
cross-posted from: https://programming.dev/post/13437386
The author’s profile says this:
“Have taken up farming.”
“Have taken up farming.”
finally touching some grass
nasal congestion intensifies
Based on the commit messages the last REAL update was 5 years ago.
most popular fork - hyfetch
I don’t understand the fascination with a program that tells you what kind of system you’re using. I’m not trolling. Can someone enlighten me on its usefulness beyond “yep, that’s what my system looks like”?
I install it on servers and put it in my bash profile so it runs when I SSH in or open a new terminal tab. Mostly just as a safety thing. It’s basically a reminder to double check I’m on the correct machine/tab before I run any commands.
That seems pretty useful, actually.
It doesn’t have to be neofetch but even in my containers and docker stuff, I try to put a little message so I don’t fuck up something.
Running through a checklist is important. I learned that from a helicopter pilot at a bar but I do think it’s true in our field. It’s not life or death on a server but training yourself to go through a simple checklist (even if it’s just “make sure this is the right terminal tab”) is good advice.
Neofetch is actually a benchmarking tool used by Arch Linux users which compete to show their high scores.
Does it have to be developed further? Neofetch looks like a finished product.
according to the Asahi guy, it doesn’t work correctly for ARM: https://social.treehouse.systems/@marcan/111018734178152229
I am utterly oblivious to how neofetch works, but it does seem to need updates to support newer tech.
Works on mine
Édit: (10)… Ah, I see the point, indeed.
Doesn’t affect me since I’m on EndeavourOS and they discontinued ARM support anyway!
It would need to keep up with future changes and any security updates
Well, it does its job for now. As for the security updates… Isn’t neofetch just a little fancy tool to display data from your system that is already exposed to any process on your distribution? What attack surface does it introduce?
Going by the releases, it didn’t need updates that often, but it still needed updates to fix and ensure compatibility as things changed
Security wise, I think you’re right