I'm a longtime Emacs user and I dabble with atom and code. The main thing that I get out of GUI editors is that extensions generally just work. I spent a lot of time debugging emacs extensions to the point that I kind of expected extensions to not work right when I install them - especially ones related to autocompletion. Nowadays I use spacemacs to keep my package management sane, but it's inflexible and complicated.

I miss things from Emacs sometimes so I keep it around. I miss macros, I miss some of the more stellar Emacs packages (Tuareg for OCaml and Cider for Clojure in particular) but I do a lot of editing nowadays in Atom and Code.

I have, and the biggest benefits for me have been:

  * Intellisense - this is *incredible*, and it works out of the box with VS Code

  * Git stuff is pointy-clicky integrated...this is a big time-saver for me, since I check stuff in just a few times a day, and I don't have to think at all about git commands after writing a bunch of C#.  I can click my way through instead.

The interface is a lot more attractive to me than Emacs has ever been (or will ever be), and I really appreciate how easy on the eyes it is, both in terms of eye strain as well as a pleasant visual style.

I'm also pretty comfortable using a mouse--i.e. I don't feel the need to keep my hands on the keyboard at all times--because, when it comes down to it, I spend a lot more time thinking than typing.

I use both VS Code and Vim very heavily every day and, honestly, there aren't really any gains or losses when switching between the two.

I use VS Code when I'm working in one codebase because it has a nice tree view of the files and has a pretty nice "working files" feature where you can easily switch between files you're working on (I usually have five or six files I'm working on at any given time; sometimes in Vim I'll open them all up in a terminal multiplexer and switch between them, but that can end up frying my brain). Seeing the tree structure just helps me visualize the codebase better. VS Code also has a really nice search feature that searches through every file in the folder you have open (I could just grep but it's convenient to click on a result and go straight to the line in that file)

Git integration in VS Code is pretty sweet as well; it has a really nice diff viewer built-in and it's easy enough to add and commit changes (I still use the git cli for branching, rebasing, etc.)

I use Vim whenever I'm in a terminal to edit various files here and there. I feel a little faster in Vim when working on one file, and I do like a lot of the shortcuts/commands a lot better in Vim. Vim also has much better find/replace with regex, and it's a lot easier to extend Vim.

I guess what I'm trying to say is that I don't see VS Code as a full-on replacement for Vim, but a different tool that I use in a different way.

I have moved part-time from vim to vscode, for Go work.

Some reasons:

- Having the full type info for every single thing in the code with simply hovering over it (not just when typing)

- Ability to "peak at definition", to get a little interspersed window with the definition of functions etc, embedded right into your editor.

- Out-of-the box file tree with single click opening, and window management (I use a lot of powerful vim commands, but window management just was too much for my head).

- Maybe something more I've forgot.

In general, the out-of-the box experience is so much greater than vim. I know you can replicate most of the above with a super-fancy setup, but I just don't find the time to get my head around much more than http://github.com/fatih/vim-go and a few personal .vimrc tweaks.

Now as others have mentioned, I just hope for a more feature-complete vim-mode in VSCode.

I'm still living in vim-wonderland, but GUI editors are more flexible in what they can show you. Underline invalid code, auto-complete, ctags pane, file view pane, etc... are all things that tend to work better in a GUI. Other things are plain impossible in TUI, such as minimap view of the file[0], or bracket's contextual popups[1][2][3]

What I'm really looking for is something like Atom's Neovim Mode [4], allowing me to use Atom's flexible UI (hey there, CSS) with vim's modal editor, wealth of plugins, and my config (keybindings, etc...).

[0] http://33.media.tumblr.com/1e4bed4a5154bf363e7f24c40eb2177c/...

[1] http://home.aubg.edu/students/PAE120/Brackets/samples/root/G...

[2] http://www.omgubuntu.co.uk/wp-content/uploads/2013/08/adobe-...

[3] https://helpx.adobe.com/creative-cloud/help/extract-for-brac...

[4] https://www.youtube.com/watch?v=FTInd3H7Zec

I'm an emacs user but I often use a GUI IDE when it makes sense. I find I'd rather use JetBrains products (PHPStorm, PyCharm and IntelliJ) even though the actual text editing part is nowhere near as powerful and efficient as my Emacs setup. Sometimes if I need to do some repetitive or monumental editing task that I could script in emacs or use the macro system, I'll switch over for a moment. The benefits of being in an environment with a debugger and many other tools as well as project management and auto-completion that is consistent across the languages I use outweigh the cons of leaving emacs. I'm considering switching to Visual Studio just for a React Native project I'm working on because it seems to handle Javascript/JMX much better than anything else I've tried.

I really wanted to use VS code with Python so I could use the debugger, but configuration see magical. I really want to like it. In the end it seems that my Django project is configured to kill VS Code when it starts up, even the menu hangs.

It might be nice editor, but it hide to much information for my taste. "You need to setup a launch.json file", well fine, but at least be a little more helpful than that, don't just open an empty file. Starting the debugger either crashed the editor or do nothing, but never informs me as to what the issue might be.

At this point Vim and shell is easier to get started with.

I don't get this false separation. Vim is, mostly, the best way to edit text, no matter the editor. Other things, like VS, Emacs, etc. are just ways to organize how the text editor interacts with other stuff (windows, IDEs, etc.).

Why not both? I use Emacs+evil. I use VS+VsVim. I don't understand why this isn't the preferred mode for everyone? Pick the best environment/shell/whatever, then make sure it uses vim for actual text editing. Problem solved.

I use vim, but Atom now primarily. Atom because of plugins: Beautify, Minimap, Markdown Preview, Convert css-to-inline, editorconfig, easy to split windows, and easy to search for text in whole directory. VSCode can't split windows horizontally but it has a nice node debug. However I usually just "node debug" in the terminal. Atom also has a Racer plugin which is nice for Rust.