It's not often I can type lol and literally mean it, but this is one of those times.. lol :D
Ever had display problems using ncurses-based programs over a serial connection? I did and I was happy to have a line editor at my disposal…
As for acme, I never got on with it. It's too graphical for my tastes: call me old-fashioned, but I like to have my finger on the keyboard when I edit (sam in a tiled wm is about as far as I'll stray in that direction). OTOH, it does have some really cool features... However, we Emacs users don't get jealous of features: we steal them...
grins evilly
I would agree with this a 10+ years ago, but I think we created better technologies since. I'd rather say that if your system is so broken you should know how to 1) snapshot it for analysis, 2) replace from original image, or orchestration. Using ed may be fun, but why not just move the snapshot to a working system instead? And apart from massive filesystem corruption, why would we ever lose /sbin in production in the first place?
Although yes, it's not the problem it used to be.
My main editor is acme, and when I need to do large edit jobs on remote servers I control I use sam. However, when I have to edit files on servers I don't control, or when I have to do a quick edit job and I don't have a sam terminal started yet, I use ed.
Unlike all other editors, ed doesn't erase the screen. I find this extremely useful. Also, ed is always the same. Vi is not always the same on different systems. Sometimes it has syntax syntax highlighting by default, forcing me to make effort to turn it off, sometimes nocompatible is set on or off, etc.
Ed is always the same and has no settings.
Sometimes inside my acme session I run win(1), and sometimes in my win sessions I ssh to some system and run ed inside acme.
I forced myself to use ed exclusively for a week some years back, and since then I stuck with it.