Re:The Rise of Microsoft Visual Studio Code
by Drdrdrq on Thursday December 06, 2018 @04:39PM
(#18622529)
> git has its problems, but it's a consistent, centralized (in the sense of origin/repo), well known set of problems.
Consistent? Ha! Change branch: git checkout my-branch. Reset file to committed version: git checkout -- my-file. Git is many things, but consistent it is not.
That said, I still use CLI precisely because I don't trust other software to make sensible abstractions on top of it, given that foundation is so inconsistent. Besides, those CI scripts only know git cli...
Re:The Rise of Microsoft Visual Studio Code
by bassman9000 on Thursday December 06, 2018 @09:15PM
(#18624565)
> Consistent? Ha! Change branch: git checkout my-branch. Reset file to committed version: git checkout -- my-file. Git is many things, but consistent it is not.
> well known set of problems
that's precisely the well know set of problems. You learn them once, apply on every console. If each UI decides to overcome them differently, you end up with N+1 different behaviors.
I'd rather have only one set if inconsistent commands, than 3.
edit:formatting
Re:The Rise of Microsoft Visual Studio Code
by umanwizard on Thursday December 06, 2018 @05:06PM
(#18622804)
Consistent in time. Those warts haven't changed much in the 7 or 8 years that I've been using git.
I use multiple IDEs/editors, and they all handle git differently. It doesn't make sense to learn yet another N sets of quirks.