Hacker News Reader

Comment by cjohansson | Hacker News Reader

I agree about this issue, maybe in the distant future this could be fixed as well but where will VSCode be at that stage? Probably even more miles ahead, due to MS funding. When there is good async support in Emacs a lot of packages would need to be rewritten.

However I prefer Emacs anyday over VSCode, I am very productive in Emacs because I'm used to doing almost everything in it

View on HN

I don't think VSCode is ahead of Emacs on some objective scale. I tried to re-create my Emacs configuration with it and found it impossible. Also VSC appeared to be notably slower when tuned closer to my needs. At the end of the day there are always users who delighted by innumerable choices of configuration possibilities, and those who believe it's unnecessary cognitive load. Emacs being DIY kit appeals to the former, while VSC is built like a browser with rich plugin system, it's in between but closer to the latter. I'm sure VSC does and will have larger audience, but only better Emacs can unseat Emacs on its side of the spectrum.

Btw the effects of MS funding can be overvalued - e.g. MsTeams is among the worst IMs in the existence.

vscode doesn't even support multiple monitors, it's far behind in many areas.

What does it mean for an editor to "support multiple monitors?"

Emacs allows you to open multiple windows that share the same local server / process and essentially work as one editor.

You can open the same or different files in the different views, use one of the views for debugging, shells, remotely running tests, while you use the other views for other stuff (showing different files side-by-side, etc.).

I often see vim and vs code users doing a lot of shuffling around when working with multiple open files to switch back and forth between files or across tabs, but with emacs none of this is really necessary.

Reply on news.ycombinator.com