Or perhaps AI code generation will "kill" both editors.

Why bother learning any editor when you do not need to write code, and there is no reason to enter

gg=G``zz

> SSH-only server administration: Vim’s sub-second startup and tiny memory footprint make it the default choice for editing config files on remote boxes, containers, and minimal Linux images where every extra process matters. It’s also nearly guaranteed to already be installed, since most base Linux and macOS images ship Vim or vi by default, unlike Emacs, which almost always requires a separate install step.

That's one way to do it. A better way to accomplish this with emacs is to use tramp mode which uses ssh as a tunnel to edit remote files in a local emacs instance. It just needs ssh access and doesn't require emacs to be installed remotely.

LONG LIVE EMACS *raises fist*!!! I still remember that old "Eighty Megabytes And Continuously Swapping" adage, but now I'm looking at my system monitor and I see several Claude instances, which can only have so much text loaded at once 'cuz context window size limit, competing with the sole Emacs instance, which has several dozen buffers on various projects open. It's wild.

That being said, I actually haven't edited anything for a while; nowadays Emacs is more of a viewer when I want to check something in a project. But actually Emacs is still fairly central to my flow as all my projects use an org file for their writeup, and that includes issue tracking, and so I have an org-edit script (communicates with an Emacs instance instead of editing the file directly) and org-issues skill that ensures that file is kept updated by Claude.