Are you sure ?
I know you see this fashionable UX as an advantage, but what I think about is how you're going to have fashionable evolution in UX thinking inflicted on you. It feels to me like someone coming into my shop and moving all my tools.
Gratuitous example from an adjacent area of nerdliness: Were you around when Microsoft decided to drop the UX they'd been using for a few decades and change to "The Ribbon" ?
Yes, I am. That's very convenient for me.
> Were you around when Microsoft decided to drop the UX they'd been using for a few decades and change to "The Ribbon" ?
I was, and you're right. Microsoft functionally owns the chrome for vscode and it isn't as configurable as far as I can tell as emacs at that layer. There's certainly a possibility they will make a decision later to mess everything up.
But for now, my previous observation stands. I have to do less configuration out of the box to get vscode into a daily use work configuration than a naked emacs install.
I highlight this because it's not an unsolvable problem for emacs. It requires making a recommended default configuration. That will be more correct for the 95% use case and advocating that configuration on the install channels for the tool.
For people interested in this, I know about Doom Emacs [1] and Spacemacs [2].
[1] https://github.com/doomemacs/doomemacs [2] https://github.com/syl20bnr/spacemacs
It is like assembling IKEA furniture if IKEA furniture didn't come with a usable manual and there are nine different descriptions online of how to assemble your new chair. Of which 5 don't actually produce a chair and two that are strangely incompatible with how you prefer to situate your couch.
Rather than be angry with people for pointing out something that is very likely to be true, how about listening to _valid_ user criticisms? And perchance see if something can be learned from it?
This is valid feedback.
I don't think that's true.
Do you include installing emacs packages as out of the box as you would vscode plugins though?
Here's what you can try: do a clean install of both, then document the steps you had to take to get VS Code + Go plugin to work vs getting Emacs to within a reasonable fraction of what VS Code will provide. Post your Emacs config when you are done. (As well as links to the sources where you found working configurations).
PS: good luck nailing the language server stuff on the first try on Emacs.
Vscode out-the-box is much more complete for coding than Emacs out-the-box.
While my Emacs-foo is not that great, I have relied on it for a lot over 25 years of programming. Recently, though, I gave Vscode a try, and while it's buggy as hell when you load up on the extensions you need, it's not that bad!
Slow? Yes, compared to a Vim or Emacs similarly set up. A wee bit bloated? Certainly, compared to my Vim and Emacs configuration.
But, really, it's the one I recommend to new developers. Not Vim, nor Emacs, even though I use those myself.
As someone who uses emacs most often: VSCode is shaped a lot more closely to a modern aesthetic by default. If you've been following along with emacs all this time and keep up to date with the latest changes, you can easily accrete the configuration to make your emacs look like a modern tool, but it doesn't start configured that way.