[penpapersw]

In my experience having switched from using one IDE to another a few times, the difficulty for me is usually that both IDEs do 90% of what I need perfectly (after a few days of tweaking), but the other 10% feels is missing and feels critical, and in particular, neither have the same 10% missing. So I kind of have to ask myself, "which critical features am I okay with giving up?" and I can't decide so I just stick with what I know and have muscle-memory for.

[bsimpson]

I'm trying VSCode now, but I still switch back to Sublime for SublimeGit. It's such an integral part of my workflow, and VSCode's built-in git is no substitute.

[komali2]

I haven't tried sublimeGit - what's it got that I'm missing from VSCode's git? I only really use it to commit and compare when I'm merging.

[bsimpson]

- You can easily see the status of each file (new, modified, or staged).

- You can easily stage all files, each file, or just specific hunks of specific files.

- You can stash and pop stashes.

- You can amend a commit.

- You can do all of that from the keyboard, without touching the mouse.

I imagine you can do many of those things with VSCode, but it's so effortless in Sublime. I haven't learned the same workflow in VSC yet, and since I do all of those things frequently, I'm really attached to SublimeGit.

[penpapersw]

In the same way, I use VS Code mostly now (for node stuff) but I still load up Emacs and use Magit whenever I need to do serious version control, meaning basically anything more than just "glance at the changes and commit everything."