Brushing over teco feels a bit .. odd given its role in Emacs but this is the vim family story.<p>Dec 10 had SOS which was an ed-like line editor. And a port of qed IIRC. It had a concept of a viewport into a file with lines longer than 80 chars, other editors did folding but this one did scrolling in ascii. Emacs now does similar. Gosling Emacs was nice before gnu. Very simple cross file macro "do this sequence of commands" mode. Vi/ex used buffers and @execute to write programs the gosling Emacs was more "do it once then ask the editor to redo it again and again"<p>Nvi and Keith Bostic deserves telling too. Kind of died
Midstream getting i8n and sub Windows fitted in.<p>The ed/sed/grep/awk unity over the syntax of the regex cannot be overstated. One investment in a syntax which embodied semantic intent in pattern match. The uplift into ex/vi was a no brainer.
AstroNvim was love at first sight for me a couple weeks ago. The AstroCommunity Rust pack gave me a super robust Rust development environment with literally just a couple minutes of setup. But as mentioned, I've only been using it for a couple weeks at this point. <a href="https://astronvim.com/" rel="nofollow">https://astronvim.com/</a>
I've now watched people go from Sublime to Atom to VSCode to Cursor. Truly it's wild how much value I've gotten out of sticking with just Vim and occasionally trimming my config.<p>I have no desire to move to Neovim. The Neovim community seems hell bent on turning Vim into another Emacs kitchen sink style ecosystem where no one values moderation and everyone is installing 100+ plugins they don't need. I haven't seen a single Neovim feature that actually helps me get work done more efficiently than how I already do it with Vim. Neovim feels like the first step since ed where the lineage has truly gone in the wrong direction.
When I was small, my dad would bring home a terminal with a thermal printer and acoustic coupler modem. This would have been mid-1970's.<p>I remember QED. I suppose it was my first editor.