>>946063
>Lots of emacs users tend to "live in" the editor; they launch it and don't close it until shutdown.
This is part and parcel with, and I'll put it another way, preferring to have an editor that's a tool in a toolbox rather than being the toolbox. (n)vim is one piece of a larger software suite I use to get things done. Not only does emacs not just slot in-place of (n)vim as that tool, but the more I drilled into it, the more it (tried to) suck(ed) me into its ecosystem. Did I mention that the things that (n)vim does out of the box requires a litany of plugins in emacs? Even shit like showing line numbers, something that requires one command in vim, either in config or as an ex command, took a less-than-zero amount of effort to replicate in emacs. Changing the background of the 81st character as a visual aid to stay under 80 characters per line, but only in latex files? Not only effort, but also couldn't be done in exactly the same way, due to some quirk in a recent update that changed the way that worked. (I think I could only set a line, not change the background, or something to that effect.) I should add too that these things that I don't use any plugins that don't come with vim. So on one hand, I have an editor I like that works the way I expect it to, that requires nothing extra to do it, and on the other hand, I had an editor which I'd wrestled into a bootleg of my original editor, required a handful of plugins to work like I'd expected, all while demanding I change my editor habits.
>run the editor as a daemon
When I was playing around with it, emacsclient, by default, ran in the terminal rather than running with a GUI, whereas straight emacs ran with a GUI by default and required a runtime flag to run in the terminal. The GUI isn't strictly necessary, but has its benefits for certain things, and I was enjoying having it available as an option. I'm sure there's a way to strongarm either the emacs binary to hook into a daemon as a client, then shove all that into a script or an alias I run instead of emacs, and retaining the benefits of the GUI while also getting the speed benefits of the client-daemon relationship, and it'd only take one afternoon to figure out, but it'd only give diminishing returns. Plus, then you have to worry about buffers. The thought of leaving something open in another buffer doesn't even enter into my mind: I close the editor, the buffer is tied to the open editor, it's all taken care of.
If you haven't noticed yet, this is a running theme in my experiences with emacs: putting in a bunch of effort to get emacs to act like vim only to get little out of it when I could just be, y'know, using (n)vim. The only thing I can say for certain that emacs could do (and do well) that vim absolutely couldn't was flyspell. But even that couldn't make me mentally justify all of the shit I was doing to emacs to make it my own.