Evidently not.
I had the good fortune to graduate from the line editors (ed, TECO) of the 70's directly to EDT (under VMS on a VAX/11-780) in the early 80's. Tried vi under Unix (Sys5) but I loved the EDT keypad programmability so much that I hacked MicroEmacs into an EDT-ish clone and ported it to all my Unix, Windows, and MacOS systems into the 90's. Used emacs for a while after that, but FINALLY AFTER DECADES OF IGNORING IT, have finally come back to using vi more than anything else, because (as Sauron points out), it works in xterms over remote connections when nothing else will. And 80% of what I do these days is over xterms to remote systems. (Sauron said "telnet" but I'm sure he really meant "ssh".)
The other 20% is typing into TEXTAREA boxes on FreeRepublic posting pages using whatever editor my browser-du-jour and OS-du-jour give me.
There's a lot to be said for the common denominator, least or otherwise.
Amen.
About the only systems that I've used extensively over the years that I didn't have a copy of vi readily available were hp-1000 and hp-3000 systems running RTE-A and MPE-V respectively.
One thing that really kind of upsets me is that some lame nerd stole my copy of the O'reilly vi reference manual. That is total suckage. Every time I thumbed through that, I'd find something that vi can do that I didn't know about.
The only editor I've ever really liked as much as vi was Brief. There's some stuff that Brief would do (Though it was strictly DOS only), that I still haven't found anything else to replace it with.
No, with some of the legacy systems I support, it's plain vanilla telnet