.Vi. are the Unix CLI companion, when a CLI UI it's not enough Unix have offered a 2D UI to do more, a bit violating Unix principles but still relatively integr

.Vi. are the Unix CLI companion, when a CLI UI it's not enough Unix have offered a 2D UI to do more, a bit violating Unix principles but still relatively integrated in Unix ecosystem/IPCs/model. Embedding, meaning copying the UI, something like evil in Emacs, it's a bit a nonsense because the strongest point of .Vi. is the Unix model witch is not a 2D DocUI model. Yes modal editing is powerful and yes in both ".Vi. alike editing vs Emacs editing" you can get powerful performances superior to any other "text editor" we have ever seen so far BUT that's not the point, the point is the role of the editor inside a broad system. Emacs is an ecosystem, incomplete since it lacks a proper LispM underneath, but closely similar to classic Smalltalk workstations, a single tool that do anything inside the tool itself, user programmable and fully exposed to the human user. .Vi. on contrary shine in a CLI unix environment. Both fall short outside their own ecosystem: Emacs fall short when you have to be outside Emacs, .Vi. when you are outside of Unix model. The point is that a powerful desktop is a single-application, user-programmable live framework like original desktops, modern systems are designed for commercial purposes as a kind of Babel's tower of insulated stuff anyone self-contained and badly fit together in an "OS+.*". You can't escape this trap. Or the entire system works integrated or you just add a bit of sugar witch might or might be not helpful but it will fall short anyway.