pro_grammer@programming.dev to Linux@lemmy.ml · 6 months agoNeofetch development discontinued, repository archivedgithub.comexternal-linkmessage-square72fedilinkarrow-up1405arrow-down12file-textcross-posted to: technology@hexbear.netopensource@lemmy.ml
arrow-up1403arrow-down1external-linkNeofetch development discontinued, repository archivedgithub.compro_grammer@programming.dev to Linux@lemmy.ml · 6 months agomessage-square72fedilinkfile-textcross-posted to: technology@hexbear.netopensource@lemmy.ml
cross-posted from: https://programming.dev/post/13437386 The author’s profile says this: “Have taken up farming.”
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up2arrow-down17·6 months agoProbably should be rewritten in a more secure language because it fetches important system data
minus-squareleopold@lemmy.kde.sociallinkfedilinkEnglisharrow-up44·edit-26 months agonearly your entire system is written in C and you’re worried about a simple fetch program
minus-squarecorsicanguppy@lemmy.calinkfedilinkarrow-up2·6 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·6 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!