In VS Code it's certainly easy to install an extension. Some mystery thing happens, and there are new commands available and some programming language support might be enhanced, but it is all very opaque. If I wanted to debug the code, I have no clue where to start. I'm sure it's there somewhere but all this looks to me much less discoverable than in Emacs.
The real problem with Emacs is the shitload of bugs that case weird, undocumented and annoying behavior. A scripting language like elips is not meant for programming something as large and complex as Emacs.
Could you name a few of these "bugs"? I use Emacs for practically everything and bugs are very difficult to encounter, even on Emacs HEAD.
> A scripting language like elips is not meant for programming something as large and complex as Emacs.
Well, that's just plain wrong. A lot of vanilla Emacs functionality is written in Elisp.
But any elisp package will have lots of annoying small day-to-day bugs and glitches.
I disagree. That's a broad and false generalization. Most packages are bug-free. If you're submitting to MELPA you need to make sure your package works and follows some guidelines for namespaces and organization, which can all the checked within emacs itself. Every package on a package tracker is vetted by at least one external dev.
Emacs functions usually require little to no modification for years, because the core is very stable.
I agree Emacs has too many bugs (but I haven't found anything that suits me better for maintaining notes and to-do lists and such).
For my config, beyond setting variables I mostly copy/pasted. It gets you very far.