This would have been the perfect time to pivot away from Google Groups & Microsoft GitHub
The Future of the Vim Project
111–120 of 376 posts
Re: The Future of the Vim Project
#112What 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?
I tried switching recently, mainly because I wanted treesitter. I couldn’t get it working after half a day messing about, a lot of documentation seemed out of date, and I don’t think my standard plugins + .vimrc worked out of the box. My main focus is getting things done, not fiddling with configs and versions, so I gave up. I figure I’ll try again in a couple of years if it’s still tempting.
I copied .vimrc to .config/nvim/init.vim, did a :PluginInstall and was up and running.
Re: The Future of the Vim Project
#113Earlier quoted context omitted.
I would not be so prompt to compare the situation with Apple and Jobs. Apple is a company that provides something no one else does while also holding a lock on its users. You can't go and install iOS apps on android. On the other hand, vim and neovim are almost the same thing, and wherever they diverge, it is always to the detriment of vim. I would not be very optimistic for the future of vim considering that nobody…
Where will they find people willing to continue working on vim's code base the same place where neovim found its developers. if one group of people can organize themselves to maintain and develop their version of vim. so can another. i don't know how many contributors vim has, but i am sure they can figure out how to move forward. finding new leadership can be difficult when there is no clear candidate, but if the co…
Bram, for 98% of the commits/lines, plus some statistical noise.
Re: The Future of the Vim Project
#114Earlier quoted context omitted.
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.
Neovim is a superset of vim, so this argument applies to both.
Re: The Future of the Vim Project
#115Earlier quoted context omitted.
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.
Neovim is a superset of vim, so this argument applies to both.
Re: The Future of the Vim Project
#116Earlier quoted context omitted.
I'm lucky enough to never have been put in this situation, so please excuse my ignorance: why does someone need to be able to sign in to my accounts when I'm no longer?
When my father in law passed away his wife asked me to get some photos on a thumb drive for her. I knew his password from watching him login, I also went ahead and deleted his browser history.
Re: The Future of the Vim Project
#117My 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'm lucky enough to never have been put in this situation, so please excuse my ignorance: why does someone need to be able to sign in to my accounts when I'm no longer?
Re: The Future of the Vim Project
#118My 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…
Another consideration, when my dad passed we had his passwords but not his phone or tablet pins/patterns. Both devices are encrypted, and the samsung I believe is set to wipe after a number of failed attempts. While there probably isn't anything on them, it's always been a pain to not know.
I know I wouldn't care because I'd be dead, but I really do not want my family getting on to my personal devices after I'm dead. Those are things that I will never give them the passwords for, not everything is their business.
Re: The Future of the Vim Project
#119Earlier quoted context omitted.
Another consideration, when my dad passed we had his passwords but not his phone or tablet pins/patterns. Both devices are encrypted, and the samsung I believe is set to wipe after a number of failed attempts. While there probably isn't anything on them, it's always been a pain to not know.
> While there probably isn't anything on them, it's always been a pain to not know. I know I wouldn't care because I'd be dead, but I really do not want my family getting on to my personal devices after I'm dead. Those are things that I will never give them the passwords for, not everything is their business.
Re: The Future of the Vim Project
#120What 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?
> what is it that outweighs all that neovim has to offer? You should ask, and answer, the question in reverse. What does neovim offer me, as a regular vim user? I don't see anything particularly interesting for my usage, so I don't have any reason to change. Also, some features are missing (like gvim-gtk, that I enjoy using to edit LaTeX occasionally). Furthermore, as of today, plain vim has an aura of venerability d…