pro_grammer@programming.dev to Linux · 8 months agoNeofetch development discontinued, repository archivedgithub.comexternal-linkmessage-square72fedilinkarrow-up1393arrow-down12file-textcross-posted to: libre@hexbear.nettechnology@hexbear.netopensource
arrow-up1391arrow-down1external-linkNeofetch development discontinued, repository archivedgithub.compro_grammer@programming.dev to Linux · 8 months agomessage-square72fedilinkfile-textcross-posted to: libre@hexbear.nettechnology@hexbear.netopensource
cross-posted from: https://programming.dev/post/13437386 The author’s profile says this: “Have taken up farming.”
minus-squareGolfNovemberUniformlinkfedilinkarrow-up2arrow-down13·8 months agoProbably should be rewritten in a more secure language because it fetches important system data
minus-squareleopold@lemmy.kde.sociallinkfedilinkEnglisharrow-up40·edit-28 months agonearly your entire system is written in C and you’re worried about a simple fetch program
minus-squarecorsicanguppy@lemmy.calinkfedilinkarrow-up2·8 months agoDid C ever generate bloated or insecure stuff for you? I had a completely different experience so I’m curious.
minus-squaresteeznson@lemmy.worldlinkfedilinkarrow-up2·8 months agolmao re-writing screenfetch in rust to avoid undefined behaviour is peak rust. I don’t want to check github because I’m sure dozens of these will exist!
Probably should be rewritten in a more secure language because it fetches important system data
nearly your entire system is written in C and you’re worried about a simple fetch program
Did C ever generate bloated or insecure stuff for you? I had a completely different experience so I’m curious.
lmao re-writing screenfetch in rust to avoid undefined behaviour is peak rust.
I don’t want to check github because I’m sure dozens of these will exist!