☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 9 days agoVSCode-style TUI written in Rustcodeberg.orgexternal-linkmessage-square12linkfedilinkarrow-up151arrow-down110cross-posted to: opensource@programming.devrust@programming.devrust@lemmy.ml
arrow-up141arrow-down1external-linkVSCode-style TUI written in Rustcodeberg.org☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 9 days agomessage-square12linkfedilinkcross-posted to: opensource@programming.devrust@programming.devrust@lemmy.ml
minus-squareHolla@feddit.orglinkfedilinkarrow-up6·9 days agoThey’re writing whole paragraphs in their commit messages. What dev would even write that much documentation at all? And then into the git message? https://codeberg.org/vitali87/croft/commits/branch/main?page=2
minus-squareTruePe4rl@lemmy.mllinkfedilinkEnglisharrow-up4·9 days agoThe fact that there is this section in the README even though all the code has docstrings and you can generate the docs is certainly interesting.
minus-squareyuman@programming.devlinkfedilinkarrow-up5arrow-down2·9 days agoif it ain’t stated front and center that this project wasn’t vibeshat, you can safely assume it is.
minus-squareSlimePirate@lemmy.dbzer0.comlinkfedilinkarrow-up3·8 days agoThe readme is gigantic with weird info like keybinds and project layout, especially the bizarre “what works” status section and the mention of number of unit tests.
how do you tell?
They’re writing whole paragraphs in their commit messages. What dev would even write that much documentation at all? And then into the git message? https://codeberg.org/vitali87/croft/commits/branch/main?page=2
The fact that there is this section in the README even though all the code has docstrings and you can generate the docs is certainly interesting.
if it ain’t stated front and center that this project wasn’t vibeshat, you can safely assume it is.
The readme is gigantic with weird info like keybinds and project layout, especially the bizarre “what works” status section and the mention of number of unit tests.