[citrusx]

Two things about VSC, in comparison to Atom, that are Done Wrong: 1) Extensibility. There's like a dozen times more friction involved in creating a plugin for VSC than for Atom. Atom was built to be as easy to change as a web app. They also created apm, which is sort of a clone of npm, for installing plugins. 2) Configurability. I can set personal keyboard shortcuts very easily, and in a way that's easily transportable between installations. I can create a new theme in minutes. Also, the way it handles the config for individual packages is well thought out. Plus, I can tarball my packages directory, extract it to a new machine, and it's basically ready to go with everything.

It's very possible for VSC to improve in these areas. In fact, I'd love to see an "Atom mode" that changes the UI/UX to more closely resemble Atom (and, somewhat by extension, Sublime). You laugh, but there's a reason that every editor takes a swing at a "vim mode". People get comfortable with the aesthetics of their tools.

[mises]

> there's a reason that every editor takes a swing at a "vim mode". People get comfortable with the aesthetics of their tools.

To be fair, vim is radically different in terms of navigation, keybindings, capability, etc. than your average gui-based text editor. I am not saying that your point is wrong, but vim is sort of an extreme example of a. the difference between vim vs. other editors, and b. the zeal with which vim users tend to cling to it (as a vim user).

[si1entstill]

It looks to me that keyboard configuration is pretty similar:

https://flight-manual.atom.io/using-atom/sections/basic-cust... https://code.visualstudio.com/docs/getstarted/keybindings#_k...

With VSCode, I haven't had any trouble moving my keybindings file between installations, even between my Windows and Mac environments (I do the same with my theme, and it works great as well).

What functional difference between the configuration styles did you run in to?

[PurpleRamen]

Simple is not always better. Especially with plugins you often also want a certain level of quality, organisation and control. I don't know much about the difference between Atom and VS Code on that front in detail, but compared to the more customizable editors (Emacs, vim, Sublime) I was always impressed with the quality of VS Codes plugin-system. While Atom made for a more messy impression, and it was at last the reason why I started to use VS Code more as a side-editor, instead of Atom.

[asdkhadsj]

Funny, I just commented on my desire to pick one of the top editors to write a complex plugin in.

While VSC sounds like a better editor, I want to write a multi-cursor, modal based editor with some UI tweaks. Ideally I'll use Xi long term, but I'd like a prototype working first. By your description, it sounds like I should stick to Atom for plugin development then?

[citrusx]

I think you'll find that it's easier to do in Atom. However - Atom's API is also probably easier to shoot yourself in the foot with.

Maybe try getting started on both, and see which one is easier or more comfortable?