I tried showcasing emacs can perfectly replace VS Code.

Never gets old to showcase this, good job

While I won't argue with you that emacs is a lot more powerful VScode, what you're missing in the video is the time and effort it takes to get emacs to that stage. VSCode on the other hand is an out-of-the-box experience.

Not questioning the premises here but, as already mentioned by u/jmhimara, you should have mentioned all the tweaks and time needed to get Emacs to just look/act like am out-of-the-box VSCode. It's a *tiny* little bit more demanding than what the video suggests ;) Imho, telling people the tool they use (and obviously, must be working well enough for them) is 'shit' may not be the best way to get most of them to even consider the alternative you're promoting. No matter how good/better this alternative actually is.

Indeed. I don't care for vscode, but it is demonstrably not shit. Microsoft have made huge strides with their open source contribution, particularly LSP, so we really need to move on from the 90s mindset.

WTF yo gi oh player and emacs user ....

Couldn't agree more.

There are a variety of things I feel are missing from this because it takes the stance of an elitist view who won't fully compare and contrast. Let me put down a few reasons. **Not only just the out-of-the-box experience, but they neglect to show the settings page and extensions area of VS code.** The reason so many people favor VS code is because it is easy to pull an extension and get into the action instantly, modifying the settings on the fly. Comparing and contrasting the emacs package manager to the vs code extension bar. Comparing and contrasting the emacs LISP configuration files compared to the VS code settings page+json file. That would be necessary to show why emacs is better. **Calling vscode extensions extremely buggy without exampling this is highly insulting to that community.** If you have visual and verified examples of this it would be a solidifed argument by experience but this is not present. **Saying VIM control is bad in VS code compared to EVIL in emacs** Why? If you don't share this it comes out hollow, especially if you are calling out people who use VIM in VS code as "people who think they are pros". **My thoughts** I use emacs and VS Code both on the daily, and I most certainly prefer using emacs. However, I feel this type of opinion puts a bad light on the emacs community. Installing emacs out of the box and attempting to use it without having studied anything first is already a gigantic turn away from most users, and that is why spacemacs exists to provide that experience. VS code does not have a packaged project like spacemacs because it does not need it. I too would love to see more emacs users, same as the author concludes in his video. we won't get them by telling them their current editor is terrible and saying you can do better, but by showing them what possibilities await them over here that they can explore.

I'm fully on board with Emacs but it's pretty damned nice to open up a go file and have VSCode auto install everything needs to get LSP and debugging up and running. I've had my LSP setup break on emacs on multiple occasions. I've got easily 1000 man hours of time in Emacs to get it where I want it. I seriously doubt you would get the average coder to invest that amount of time into their editor.

config please

IMVHO (sysadmin) VS Code should be considered *crap* simply because underneath Electron and the fact that's a modern application crafted as most big modern applications... Beside that consider a thing: VSCode root itself on so big codebases that's it's future is unknown, essentially no community can really maintain it, and even big of IT can't really maintain monsters like modern WebVM in their few forms, you can readily use it of course, but all you learn will go to the bin at an unknown point in time. You can't really "grow" on such platforms. Modern GUIs are designed in a desperate move to avoid giving power to the user, not joking. Classic UNIX at least provide a way to use the system, via IPCs and scripts. Classic UNIX GUI was somewhat extensible. Modern GUIs are monsters that knowing the widget based model is too limited they try to resemble a doc-style UIs from the past becoming dysfunctional monsters in the process.

A bit aggressive for my taste; VS Code is a great piece of software, and the criticisms need a little more justification so they aren't just "cranky emacs guy," which is a true stereotype I want to see broken. That said, I love the feature comparison and the setup you are able to demonstrate.

I agree that emacs is an awesome editor (perhaps the greatest), but this vid is way too harsh on VSCode. If it weren't for VSCode, the emacs and neovim community would perhaps take another decade to figure out all the modern things users want, not to mention LSP. VSCode single-handedly "inspired" these old-school editors to move on with time -- we should give it more credit -- it deserves them.

This is less "cranky emacs guy" and more "zealous convert". Typical of someone with a lot of free time, relatively speaking, who's just discovered what Emacs can do. "Just" is relative to Emacs' age, so perhaps in their first 1-2 years of using Emacs. Strident opinions like the ones in this video are the purview of both the startstruck novice and the tired veteran.

[deleted]

LSP is probably one of the best things to happen to emacs in a long time, and is just a great idea. The set of people that know how to analyze a language *and* that know elisp is always going to be smaller than the set of people that know how to write a good LSP server.