What is it that prevents the rest of the vim community from adopting neovim? From what I can observe, a great deal already have. But for the folks holding out, what is it that outweighs all that neovim has to offer?
gvim and vimscript9
The Future of the Vim Project
121–130 of 376 posts
Re: The Future of the Vim Project
#122What is it that prevents the rest of the vim community from adopting neovim? From what I can observe, a great deal already have. But for the folks holding out, what is it that outweighs all that neovim has to offer?
Ubiquity. I have Vim on every machine I log into without installing anything extra.
With caveats:
- Different servers may have different versions of the program. Some distros are very "stable" and have very old versions of programs.
- It's common (especially for vim) for users to have significant configuration files to make use easier.
Re: The Future of the Vim Project
#123Earlier quoted context omitted.
It's not an implementation from scratch, do you know the history of the projects? Neovim started out as a large clean up and refactor of Vim code, plus the addition of async code. That's a huge amount of work, partially re-implemented by Vim (Bram implemented his own version of async). Actually, after the Neovim launch a lot of the Vim features were just Bram chasing after Neovim features. Vim9script, :term, etc. I t…
Bram evidently had his own way, since he didn't let anyone else make commits to the project. That's fair, and in that situation forks are expected.
I’ve seen some reports that he did allow commits but he would “re”-commit them as part of his workflow. I’m not sure about the reasoning there.
Re: The Future of the Vim Project
#124Can someone copy-paste the text, please? I cannot read it because Google hates Firefox users apparently.
EDIT: The Internet Archive has a functional copy. https://web.archive.org/web/20230810094255/groups.google.com...
Re: The Future of the Vim Project
#125My brother passed away very suddenly a few years ago, and I was put in charge of wrapping up and archiving his "digital" life. We were very lucky that we had access to a recovery email for his main gmail account (as well as a couple of passwords that his partner knew) and was able to access and archive virtually all data we could think of (services like Google Takeout were invaluable). I realized that if this had hap…
Useful checklist: https://getyourshittogether.org/
Others in this thread have talked about safety deposit boxes and buried crates. I'd add that you can just give some trusted party a normal encrypted USB flash drive, and eliminate the risk of getting absolutely rinsed out in the event of a house burglary by splitting the password amongst an arbitrary number of your other contacts using the Shamir's Secret Sharing algorithm.
Re: The Future of the Vim Project
#126This would have been the perfect time to pivot away from Google Groups & Microsoft GitHub
Google groups I can't comment but Github is a relative new thing. They were also still accepting patches on the mailing list(I believe the github pull request were mirrored to the ml or something like that). Bram was often replying to issues and pull request via email so github adoption doesn't seem to what Bram wanted. So no migration away from github.
Re: The Future of the Vim Project
#127Earlier quoted context omitted.
Maybe not important to some but the ability to use Lua over VimScript is a big win in my opinion. In fact, I use a mix of thr two where necessary.
How much of the rest of the vim ecosystem is Lua-based, though? As far as I know it's still mostly vimscript. Vimscript's dominance in vim is one of the things that got me to switch to emacs when I got interested in Lisp and Scheme more than a decade ago. Sure, even then I could write scripts for vim using Vim's scheme compatibility mode, but I'd probably be one of the only ones doing so. Pretty much everyone else wa…
> How's the vim ecosystem now? Is vimscript still dominant?
You can have a full neovim experience with all sorts of modern extensions without using a single line of vimscript. Some people even replace their init (neovim's vimrc) with lua, but I am of the opinion that it is a step too far, as lua isn't particularly adapted to writing configuration files and the result is too verbose to my taste.
Re: The Future of the Vim Project
#128What is it that prevents the rest of the vim community from adopting neovim? From what I can observe, a great deal already have. But for the folks holding out, what is it that outweighs all that neovim has to offer?
From what I remember, NeoVim drops vi compatibility mode. vi is part of POSIX. That alone would be a reason to mantain Vim as a modern superset of vi.
In what circumstances would you run `vi` and find yourself upset that you end up in `vim`?
Re: The Future of the Vim Project
#129What is it that prevents the rest of the vim community from adopting neovim? From what I can observe, a great deal already have. But for the folks holding out, what is it that outweighs all that neovim has to offer?
MacVim and gVim. I've looked at neovim and there are many GUI options (paradox of choice), some of which I've tried, but at the end of the day, I'm more comfortable with what I'm already familiar with.
Likewise. I’m a heavy CLI user but gVim/MacVim are so entrenched in my workflow that the lack of a stable GUI for Neovim made it pretty much a nonstarter for me.
Re: The Future of the Vim Project
#130My brother passed away very suddenly a few years ago, and I was put in charge of wrapping up and archiving his "digital" life. We were very lucky that we had access to a recovery email for his main gmail account (as well as a couple of passwords that his partner knew) and was able to access and archive virtually all data we could think of (services like Google Takeout were invaluable). I realized that if this had hap…
I've had this[0] bookmarked for a while. A good list of things to keep note of somewhere safe. Probably the old "3-2-1" backup method at minimum.