Live data from Hacker News

The Future of the Vim Project

groups.google.com

141–150 of 376 posts

Re: The Future of the Vim Project

#142
post #52

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?

Well, why should I? I don't need a reason not to do everything, by default I'm not doing things, it's changing from status quo that requires a reason.

It's easier to maintain one codebase than to maintain two forks.

If development of vim dropped and neovim was nominated as its successor, I'd think most vim users would be just fine.

Re: The Future of the Vim Project

#143

Earlier quoted context omitted.

> 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…

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.

> the ability to use Lua over VimScript

The Neovim people went a bit further with the integration, but you've been able to use Lua with Vim for like 20 years or so, and you can use it to write perfectly functional plugins with it. Probably the main difference is that in Neovim Lua is always guaranteed to be available, which isn't the case for Vim.

Re: The Future of the Vim Project

#144

Earlier quoted context omitted.

Anything with recurring billing needs to be cancelled, for a start.

Call the deceased person's bank to cancel all credit cards in their name and that's taken care of.

You'd think it's that easy. Some places literally are unable to do anything unless you're some sort of "signatory" or the actual account holder. No amount of if, buts, maybes, and certified/stamped copies of death certificates will convince them.

I couldn't even cancel the health insurance company's recurring payments after a death. And they had the audacity to send a "how was your hospital stay" questionnaire to the account holder's email after they were "discharged" by the hospital.

Re: The Future of the Vim Project

#145

Earlier 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…

I think the ecosystem is more or less splitting. As a user, not dev, it looks like neovim "distributions" are mostly lua and would be feature complete (with some substituted plugins) even if 100% lua was enforced.

Re: The Future of the Vim Project

#146

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?

Loyalty? Inertia? I never felt like there was a reason to switch. I admired Bram’s work on Vim, still do, and didn’t see any benefits to switching. Still don’t, as long as the rest of the Vim dev community are willing and able to carry it forward.

For my purposes, Vim is complete. I don’t require new features, as long as it is maintained and runs on modern OSes.

Re: The Future of the Vim Project

#147
post #127

Earlier quoted context omitted.

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.

I have mainly lua config but just put in some vim files where I put bits and functions that were already written in vimscript.

Re: The Future of the Vim Project

#148
post #13

My 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…

My brother-in-law's mother passed away last year and he was in a similar situation. Even beyond the digital realm, there are so many details in a person's life that have to be attended to. Insurance, mortgage, vehicle ownership, etc etc. It's really an overwhelming process and it took a toll on him.

I've been thinking about building a platform to help prepare for and guide families who are faced with this kind of situation.

Re: The Future of the Vim Project

#150

Earlier quoted context omitted.

LastPass let you put two emails as your family members and you setup a 30 day limit to show you are alive. If your loved ones require access to your passwords and you are not there for 30 days, Lastpass release your passwords to them

But we don't use LastPass after they have demonstrated over and over that they are not to be trusted with our secrets, right?

And it means they must be keeping the recovery passwords in plaintext, so it just gets worse...
Post reply on HN