☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 4 days agoVSCode-style TUI written in Rustcodeberg.orgexternal-linkmessage-square11fedilinkarrow-up156arrow-down111
arrow-up145arrow-down1external-linkVSCode-style TUI written in Rustcodeberg.org☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 4 days agomessage-square11fedilink
minus-squareHolla@feddit.orglinkfedilinkarrow-up7·3 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-up5·3 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-squareSlimePirate@lemmy.dbzer0.comlinkfedilinkarrow-up3·3 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.
minus-squareyuman@programming.devlinkfedilinkarrow-up5arrow-down3·3 days agoif it ain’t stated front and center that this project wasn’t vibeshat, you can safely assume it is.
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.
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.
if it ain’t stated front and center that this project wasn’t vibeshat, you can safely assume it is.