VS Code is set to rule the developer world. The core and extension model is designed beautifully. While the core editor is concentrated at performance, the extensions provide feature rich functionality for each developer needs.
Otherwise it is a wonderful peace of software.
But, setting that aside, I was begrudgingly impressed. I was conditioned at an impressionable age to be revolted by anything Microsoft, and VS Code mostly won me over.
I still prefer emacs, but only because I haven't managed to customize VS Code to match my workflow (that might be impossible for now given that I spend about half my time working in Clojure).
The key bindings are incredibly configurable and recent versions have added a really nice GUI for it (over just manually editing the JSON configs).
https://code.visualstudio.com/docs/getstarted/keybindings
The configuration of key bindings has been put through the ringer by the vscodevim extension, which has long been one of the "first customers" of the key binding configurations. If Vim can bind a key to it, for the most part so can you. There are very few functions in the application that you can't key bind if you wish.
Furthermore, extensions can contribute key maps and there are key map extensions based on a number of other editors already as extensions. A link right below the key binding configuration takes you to a recommended extension list.
It is interesting that VSCode defaults to a relatively small key map, encouraging you to explore commands through the command palette instead, but VSCode seems to make up for that by giving you a lot of power to customize as you see fit (and extension capabilities to share those customizations with others).
"files.eol": "\n", // blah blah some comment here
I think it also has a notification in the lower right, LF and CRLF.
Not the best, but maybe learnable with practice?
Disclaimer: I have only played with it. I do program a little but it is not something you want to pay me to do.
This is an issue in almost every other editor that has plugins! Vim, Emacs, Sublime Text, etc have widely used automatic plugin installation tools.
You can manually download and install plugins if you're worried about a 3rd party issuing malicious automatic updates.
You can say the same about browser extensions. They have the same distribution mechanism as VS code plugins, and still there's a good number of them doing shady stuff.
I have a feeling that this approachability is what will win in the end.
It won't win me over, but my investment in Emacs can be measured in over 50kb of elisp code :)
Most developers do not care to learn VIM/Emacs, myself included.
https://insights.stackoverflow.com/survey/2017#technology-mo...
I like VS code, but emacs and vim both have healthy, large user bases. Unless the only definition of a developer is "people writing SPAs"
However statistics don't lie. Good bye 77kb emacs config, good bye editors wars. I enjoyed trolling you, VIM users, but today I saw the light.
I'm moving to Notepad++.