I just made the switch also, but from Visual Studio. (Blogged about it here: http://tiny-giant-books.com/blog/things-vscode-didnt-tell-me-about-programming-in-f

I just made the switch also, but from Visual Studio. (Blogged about it here: http://tiny-giant-books.com/blog/things-vscode-didnt-tell-me-about-programming-in-f/ http://tiny-giant-books.com/blog/things-vscode-didnt-tell-me... ) It's amazing how much muscle memory plays a role in tool adoption. The author says "The mismatch between keybindings in VSCode and rest of my tools just kept tying my fingers in knots" You can't spend years and years doing something one way unconsciously and switch without it being quite painful. I think once you're a Emacs user for a decade or more, you're probably an Emacs user for life -- or at least it's going to be painful to switch. "It is important to note that the Project Manager addon may have improved significantly since I last used it a few months ago" Yes. VsCode is a rapidly-changing environment. When I started with it this week, I had downloaded the most popular plugins just for kicks. As it turns out, there were plugins for most every common thing I do. The switch, however, was painful. Looking at my desktop, I've got a dozen editors, half-a-dozen or more IDEs. This is getting crazy. At some point, maybe Emacs is a much better long-term investment. But if you do that, you miss out on seeing what all the cool kids are doing -- and that's important for a lot of other reasons besides programming (Marketing, for instance) Sidebar: People get really, really attached to their IDEs. Maybe as much or more as their favorite programming language.