Earlier quoted context omitted.
This view is obviously biased against Emacs, but I don't disagree completely with the premise. As an Emacs user, being "immediately productive" (whatever that means) is not your topmost priority. You mold your Emacs to a workflow unique to you, notice things you are doing often, add elisp functions to change it to make those things easier, and carry them with you from job to job. As your job evolves and changes, you…
> You mold your Emacs to a workflow unique to you, notice things you are doing often, add elisp functions to change it to make those things easier, and carry them with you from job to job. As your job evolves and changes, you maintain and grow your Emacs files over decades, and borrow from someone else's workflows. I've been writing software for ~24 years, and I can understand the need for this in the past. Now, I ju…
-Remote file editing with Tramp: This is much better even than using vi/pick over a terminal.
-Very flexible kill ring copy paste mechanism: can do complicated text manipulations with easy access to copy paste history.
-Easy macro recording and playback.
-Very flexible windowing: can show even multiple windows with the same file, even synchronized scrolling of required.
-Rectangular/column edits.
-Built in file manager.
-Built in shell, can run shell programs and capture their output.