Don't get me wrong, I do get and appreciate the "complete package" and "customize everything" approaches followed by Emacs, but Emacs is often not the best tool for the job, if you work in a team. You've mentioned Jupyter notebooks and project management. Yes, Org and interactive modes are excellent, well-polished, full of goodies. The problem is that features like these require other people to either do the same as you do or to be able to integrate via an API/protocol. Having lots of people being fond of Emacs is a bit of a stretch, while integration features rely a lot on the community, which, as I've already said, isn't that wide, so plugins aren't always well maintained, unless you do it yourself, of course... And as a editor with LSP (a built-in) Neovim is simply put extremely responsive, I'd say it's closer to Unix philosophy of having a single thing doing its job really well.
You're missing the crux of the matter. It's not about comparing the quality of two distinct tools. It's erroneous to claim that a power drill is inherently superior to an oscillating spindle sander - these are tools from different categories, each excelling in its intended purpose. Certainly, tools can sometimes be repurposed for tasks they weren't designed for, and occasionally this leads to the creation of a more suitable tool, but that's the exception rather than the rule.
I use both Vim and Emacs daily, and while your observation about Emacs generally being slower than Vim isn't incorrect, it doesn't necessarily make Vim a better all-purpose tool for everything. Emacs isn't either, for certain things, Vim is indeed excellent.
I suggest you reconsider your perspective on Emacs users as mere dorks who misunderstand Vim or are too lazy to learn it. Instead, explore their motivations, question your own "cold attitude towards Lisp-like languages" - "know thy enemy", if you will. You might uncover some surprising insights. Trust me on this, from one die-hard Vimmer to another: it's never "Vim vs. Emacs for everything", it's rather "Vim or Emacs for the task at hand".
I don't hate on Emacs in general, even more so I'm quite happy to learn about it's features and great plugins, but that'd mean a decent time investment. From my side, I'm generally a slow learner too, it took me a few years to be productive in Vim/Neovim, configuring it to my liking, polishing the motions. Maybe if I get some more free time with the new job, I'll finally go about making my Emacs config work well.
