This is a damning indictment of file systems. We have enough cheap space that we... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		eterm on April 7, 2022 \| parent \| context \| favorite \| on: Use Git tactically This is a damning indictment of file systems. We have enough cheap space that we should be able to easily have (non-binary) file changes have a history log in our file system itself and be able to revert local changes without needing the full change graph that git entails. I'm all for small commits, but committing every time ctrl+s happens would be an anti-pattern because ctrl+s doesn't imply it compiles whereas I'd want any commit to compile. (passing tests optional).

layer8 on April 7, 2022 | [–]

Windows has File History, which I sometimes use to restore a file or directory to a prior state.

Also, some editors/IDEs have a file history function (separate from version control).

spindle on April 8, 2022 | [–]

Strongly agree. To some extent, one can use a snapshottable file system like ZFS for this.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact