Why Emacs: Redux
What made me switch to VS Code (after using Emacs for 30+ years) was that I got tired of just how much of an easter egg hunt Emacs is for me now.<p>Setting up Emacs reasonably for Go development just isn&#x27;t even close to being straightforward.  And with Go, go tooling and Emacs continually being changed, any setup that works will eventually stop working and you have to try to figure out how to rewrite your configuration.  This happens often enough that even someone like me, who really, really didn&#x27;t want to ditch emacs, eventually may do so.<p>I appreciate all the work that has gone into Emacs, but the feeling I get is that the project lacks enough active developers and&#x2F;or the focus misses the mark.  I see version numbers going up - I don&#x27;t see visible improvement.<p>The goalposts moved.  They are farther afield.  Expectations of what an environment has to offer have gone up.  If a decent developer experience isn&#x27;t an understood priority, then Emacs isn&#x27;t going to be very attractive for new developers.  And it may have problems both attracting new users and developers and retaining new developers.<p>(That being said: VS Code is apparently going through a rough patch where things have gotten <i>really</i> buggy if you use it for Go development.  So it isn&#x27;t like VS Code is a magic bullet)