4 ms·

I moved from Atom to VSCode a few years ago. It's a worthy successor, in my opinion. What were your blockers to moving to VSCode? My remaining issue is to be a

I moved from Atom to VSCode a few years ago. It's a worthy successor, in my opinion. What were your blockers to moving to VSCode? My remaining issue is to be able to css style any element of the UI like I could with Atom. There're plugins that let you monkey patch to get that feature, but updates to VSCode break them.

mgaunard 4y ago
Too many windows, panes, misfeatures I don't want, and it's also quite slow. It's a kitchen sink even before you install any plugins, and yet all the useful functionality requires plugins. All I want is a text editor that can quickly switch to another file, that doesn't make it annoying when the file it had open was changed, that only adds the input that I type to a file and nothing else. Also easy integration with commandline tools (select text, pass that as stdin to a command, replace it with stdout, all done trivially without going through a billion menus and plugins), vertical selection and multi-cursor that doesn't suck, maybe a few other details, are things where it failed to deliver.