pro_grammertoLinux@lemmy.ml·6 months agocross-posted to: opensource@lemmy.mlNeofetch development discontinued, repository archived(github.com)external-linkarrow-up1405arrow-down12message-square72file-textfedilink
arrow-up1403arrow-down1external-linkNeofetch development discontinued, repository archived(github.com)pro_grammertoLinux@lemmy.ml·6 months agocross-posted to: opensource@lemmy.mlmessage-square72file-textfedilink
cross-posted from: https://programming.dev/post/13437386 The author’s profile says this: “Have taken up farming.”
minus-squareGolfNovemberUniformarrow-up2arrow-down17·6 months agolinkfedilinkProbably should be rewritten in a more secure language because it fetches important system data
minus-squareleopoldEnglisharrow-up44arrow-down0·6 months agoedit-26 months agolinkfedilinknearly your entire system is written in C and you’re worried about a simple fetch program
minus-squarecorsicanguppyarrow-up2arrow-down0·6 months agolinkfedilinkDid C ever generate bloated or insecure stuff for you? I had a completely different experience so I’m curious.
minus-squaresteeznsonarrow-up2arrow-down0·6 months agolinkfedilinklmao 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!