News for hackers. Stuff that matters.
Re:The Rise of Microsoft Visual Studio Code by bassman9000 on Thursday December 06, 2018 @01:41PM (#18620787)
amen

people look at me like I'm an old crazy dude because I don't use a git UI or eclipse, or intellij, or from sublime. Git already has plenty of quirks, adding another layer of unknown on top of it is a no-go

Re:The Rise of Microsoft Visual Studio Code by emerongi on Thursday December 06, 2018 @03:02PM (#18621578)
I've started using VSCode for git push/pull/branch and staging. This is what I use git for 99% of the time anyways and since they are simple commands, triggering them from VSCode is faster than falling back to CLI.

Staging/diffing is especially convenient with VSCode. `git add -p` used to be my most-used command, but VSCode just makes the process easier.

Re:The Rise of Microsoft Visual Studio Code by gknoy on Thursday December 06, 2018 @05:41PM (#18623174)
If you stage things often enough, `git add -u` might be enough. It's pretty much what I use all the time, aside from the few times I do `git add -up`.
Re:The Rise of Microsoft Visual Studio Code by kstrauser on Thursday December 06, 2018 @03:35PM (#18621930)
My most famous quote in my work Slack is: "git already has a luxurious client! it’s called git and has lots of shinies."
Re:The Rise of Microsoft Visual Studio Code by CuriouslyC on Thursday December 06, 2018 @05:11PM (#18622842)
While I agree with this in most cases, visual merge is a huge deal.
Re:The Rise of Microsoft Visual Studio Code by freeone3000 on Friday December 07, 2018 @04:02AM (#18626100)
git mergetool will spawn the mergetool of your choice, anything from kdiff3 to vimdiff.
Re:The Rise of Microsoft Visual Studio Code by freehunter on Thursday December 06, 2018 @02:45PM (#18621370)
Which is weird because with all of its inconsistencies, git must have been designed with the idea that someone would build a sensible shell over top of it. I can't imagine Linus expected people to interact directly with git when he built it.
Re:The Rise of Microsoft Visual Studio Code by bassman9000 on Thursday December 06, 2018 @03:39PM (#18621962)
git has its problems, but it's a consistent, centralized (in the sense of origin/repo), well known set of problems.

I use multiple IDEs/editors, and they all handle git differently. It doesn't make sense to learn yet another N sets of quirks.

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.
Re:The Rise of Microsoft Visual Studio Code by bgruber on Thursday December 06, 2018 @09:10PM (#18624531)
Re:The Rise of Microsoft Visual Studio Code by voltagex_ on Thursday December 06, 2018 @09:49PM (#18624721)
OT: that's a blast from the past - http://www.gelato.unsw.edu.au/
Re:The Rise of Microsoft Visual Studio Code by dagw on Friday December 07, 2018 @04:10AM (#18626147)
Heh. As an "old dude" I'd assume that anybody using git directly would be a "young dude" who's been using git all their programming life.