3 ms·
The issue with those git guis like the vscode one or github desktop is that they fundamentally misunderstand git. they make it the default to merge current bra
by lionkor 3y ago
The issue with those git guis like the vscode one or github desktop is that they fundamentally misunderstand git.
they make it the default to merge current branch into current branch (pull with merge) and they default to committing large amounts of code under a simple message.
i know fulltime devs who use git every day, who have no idea what a rebase is - they think merge does what really rebase does, and thats mostly the fault of bad defaults.
git commit -p should be the default committing interface also; assuming you like git history which can be bisected, reverted, etc.
- yCombLinks 3y agoThat should be telling you that git is designed unintuitively, not that everyone else is wrong.
- rectang 3y agoWe can have high expectations for those who aspire to improve on Git — that they will grok its strengths, weaknesses, and underlying model thoroughly. Even if they cater to novice users, they aren’t novice users themselves and lack of experience is no longer an excuse when Git wrapper authors make bad choices about defaults.
- Hendrikto 3y agoIf that was the case, things would be different with other VCSs. In my experience, that isn’t true. The main problem is that many people just don’t care, and view VCS as an afterthought, after the actual work is done. They don’t even know how powerful git can be when used optimally. Maintaining a clean git history is work. You have to think about it, and invest into it. But it is well worth it, in the mid to long term.
- __jonas 3y agoYes exactly, I don’t care. I want to write code and not constantly spend time thinking about the structure and semantics of my version control system. I understand different projects have different requirements for version control, but as someone who does not work on massive codebases with a huge amount of collaborators I enjoy that the GUI I use somewhat hides the complexity I don’t want to engage with.
- formerly_proven 3y agoIt tells us that git supports multiple workflows and some of the defaults are for a workflow that most git users don't use.
- Blackthorn 3y agoCounterpoint: there's nothing wrong with pull with merge.