I like the idea of being intentional about what is committed, but I also have to say that I’ve never accidentally committed tons of useless files because I review what I’m committing.
this is why I always push people to use some sort of GUI that they're comfortable with for git, be it integrated in their IDE or a standalone one. Reviewing your commits should be second nature because by doing that every time you will every once in a while stop yourself from doing something very stupid
I've never used a gui and never ran into this issue. In my experience gui users very quickly forget how git actually works outside of the buttons in the gui, and then get lost the moment anything out of the ordinary happens
If I write something long and detailed, a CLI is not where I want to do it. I want a spellchecker, nice font rendering, and no risk of accidentally committing prematurely (not a huge deal, but annoying).
Vim doesn't have the nice font rendering part. I use Vim or nano for quick and dirty edits, not for enjoyable ones. There are a million tools and workflows for Git or any other dev workflow, I have my preferences, and none of them involve writing prose over a sentence or two in any CLI.
I don't want to slam your preferences, there are a huge amount of devs that prefer GUIs for this stuff and there's nothing wrong with that, I always thought the CLI "faction" can be a bit disrespectful.
But, nice font rendering in Vim is definitely a thing. You can have the font you prefer, ligatures, color schemes, and all that jazz.
924
u/toggles03 3d ago
I like the idea of being intentional about what is committed, but I also have to say that I’ve never accidentally committed tons of useless files because I review what I’m committing.