10 years of love for Emacs undone by a week of VSCode
Stuff seems to be very easy to get working in VSCode, whereas almost everything is a bit of a faff to set up in Emacs. Getting decent Go support in VSCode took about 1 minute, for example, and the only problem I&#x27;ve found with it is that now I&#x27;ve got to use Go. Emacs on the other hand... well, I haven&#x27;t even bothered. It&#x27;s almost certainly going to be a complete bind. (And even if it isn&#x27;t, my statement is worded in such a way that I&#x27;m actually still right.)<p>Once you&#x27;ve been using VSCode for a while, though, you&#x27;ll start to wonder just why you can&#x27;t move that stupid sidebar to some other place on the screen.<p>Or maybe you&#x27;ll wonder why you can&#x27;t see its individual components in different windows. Why are they all stuck as like tabs of the same panel?<p>Come to think of it, why can you only split the editing window twice?<p>And considering it&#x27;s all driven off a dynamic language, how come there&#x27;s so much damn boilerplate when it comes to writing an extension? And where&#x27;s the in-editor JS REPL akin to M-: or the scratch buffer? (Actually, now I&#x27;ve even asked that question, I&#x27;m sure I&#x27;ve just missed something obvious, because there <i>has</i> to be one, and it <i>must</i> be there.)<p>Don&#x27;t even get me started on how to share configs between multiple systems... (there&#x27;s an addon that&#x27;ll upload them to gists but there doesn&#x27;t seem to be any way to have system-specific configs, something that Emacs solves inherently because its config files are just Lisp code)<p>Also, VSCode doesn&#x27;t work properly with my favourite font on Windows.<p>And I&#x27;m not going to mention org-mode.