I guess I’ve activated to post random stories about #vim lately ;-) There’s so much hate for it, especially from some members #neovim community, so I just want to show that there is also other side of the story. In other words, there are people who pick “just” Vim purely based on technical advantages.

It is a bit over year since Bram Moolenaar died so I guess this is also good timing in that sense (RIP) ;-) Remembering that by migrating my vim files to vim9script 🍾

The last draw was complains in some places of Vim doing "incompatible changes" with Neovim. The universal law is that the upstream defines what is compatible and then it is up to forks to keep in phase. If there is compatibility issue, one can only blame the fork. Over the top disrespectful tbh...

@jarkko Х.org was technically a fork of XFree86, but we know how the story went. Neovim just did the right thing and got all the attention it deserves - because the demand was there. It is not even that vim is bad at what it does, it is just that that people expect more from an editor these days. Emacs acknowledges it (eglot, tree-sitter support) and may survive, Bram (R.I.P.) completely missed it. The rest is history.

@ringtailringo I do remember that. It was licensing controversy 🤷‍♀️

@jarkko Sure, there is always some reason, but "I was first there will not help" - it did not saved the original vi or non-gnu emacs.
Neovim has imo the best dev ecosystem right now and deserves the love it gets. Hard to choose vim over it but for most basic admin tasks.

I just wish the place would be taken by something more emacs-like, hackable and with instant eval. Both vim and neovim are pain in the *** to configure and debug in comparison. Maybe helix with scheme configs will do it better.

@ringtailringo I blindly ignore this nonsense, sorry.

@jarkko You do you. The rest will not care.