Emacs is definitely more full-featured than plain vim. But for me, I wouldn't be switching to it from plain vim, I'd be switching to it from a LazyVim setup. Which I've barely had to configure: it's an IDE straight out of the box. And to get that IDE setup back in Emacs, I'd have to learn which Emacs plugins do what, reconfigure several plugins' default keystrokes to match what LazyVim did because those are in my muscle memory now... it's a big effort. I won't rule out doing it someday, but for now it costs too much in lost productivity while I'm trying to get work done. Maybe sometime when I'm on vacation, and the temporarily-lost productivity doesn't cost as much.

But NeoVim has made writing plugins so much easier, even things like editing Lisp are getting not too bad. https://github.com/Olical/conjure has been a pretty decent substitute for SLIME, there's a paredit implementation that works well, and so on. So the need to switch is lower and lower, and the cost of switching stays high-ish, and so I haven't done it yet. Someday, as I said, I'll give it a shot.

P.S. I would be remiss in recommending LazyVim if I didn't at least once mention the really, really good https://lazyvim-ambitious-devs.phillips.codes/ book, which you can read online entirely for free. It's an excellent resource to learn LazyVim and what it adds to a vanilla NeoVim installation.

Let me share 2 words - Doom Emacs, Spacemacs.

You're right. Using vanilla emacs as an IDE means configuring evil, eglot and window management. You can use doom/spacemacs but they hinder future customizability because you'll be fighting against your config and doom's upstream changes.

Conjure looks great but IMO it's not a 1:1 substitute for tight coupling between editor functionality and internal tooling. If neovim gets 80% of the way to a productive coding setup then emacs helps hone that last 20%.