[qppo]

You can do all that and more in vscode as well... you just have to "learn to master and config" it with your own plugins in JS. It's not that hard.

[umvi]

I tend to let other people "master and config" VSCode and then I just go download their extensions. IMO that's the beauty of VSCode - critical mass

[sedev]

That's also available with emacs, though, it has its own extension ecosystem that's about as easy to access as VSCode's.

[r-zip]

VSCode isn't as flexible at all though. You can't even create a keybinding that executes multiple commands (macro). There aren't hooks. You can't just write a function in a file and execute it. There isn't the same level of introspection.

In a lot of ways, VSCode is more convenient, but its extensibility doesn't come close to matching Emacs'.

[mercer]

I use VSCode for my day to day coding, so I have nothing against it, but explain to me how I can 'do' Magit and the like in VSCode...?

[evan_]

I’m not familiar with magit but from a quick skim of the “visual walkthrough” I think you can get most if not all of the functionality either built in to vscode or with the free “git lens” plugin, one of the most popular in the extension directory.

Here’s what’s built in: https://code.visualstudio.com/docs/editor/versioncontrol

and git lens: https://marketplace.visualstudio.com/items?itemName=eamodio....

[moocowtruck]

https://github.com/kahole/edamagit

[ashtonian2]

Literally anything you can do in emcas there is an extension for or at least one in dev. Vscode will outgrow emcas given its critics mass and momentum.

[thom]

Have you found that other extension authors have this in mind? Most extensions don't seem to be built with hooks in mind so you're kinda stuck with either the existing extension or rolling your own. There also aren't very good primitives for most use cases because of this. I assume VSCode will get there though.

[qppo]

VSCode extensions are driven through "commands" that are exposed through the package.json of the plugin (which can be parsed by other plugins if you wanted) and issuable through another plugin, or using a task (this is kind of annoying though and not a first class use of tasks).