Live data from Hacker News

The Future of the Vim Project

groups.google.com

11–20 of 376 posts

Re: The Future of the Vim Project

#11
Everyone puts off estate planning in general for obvious reasons (most people don’t want to think about their own mortality) all the more so, most don’t give a thought to digital estate planning, it’s especially hard because there are very few resources to do it and most apps/websites don’t have that workflow planned out (Afaik, really only Facebook does anything for this).

My wife and I share a password manager account so theoretically she should have access to every site I use, but will she know where to go? Will she have any clue how to maintain our local self hosted services? Let alone the hardware?

I’ve walked her through restarting the esxi server and ssh’ing into the main docker server to restart it, but I haven’t documented any of this anywhere for her…

Re: The Future of the Vim Project

#12
I hope both Vim and Neovim extend olive branches (and Git branches where it makes sense! :-D ).

Even if the fork doesn't heal, if they could align the code bases to bring them closer, both sides win.

Re: The Future of the Vim Project

#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 happened to me, it would have been virtually impossible to do, as all my passwords and credentials are in my password manager, and the password to that was only in my head.

It's a good thing to plan for this eventuality, to make it easy for your family and friends to wind up your "digital life" after you've passed. 1Password has a very good solution for this, with a "recovery document" you can print out and write down your password on, which contains instructions anyone else would need to access your 1Password account. I gave a copy of this document printed out to a small number of people I trust implicitly.

You never know when something sudden can happen to you. For the sake of those you leave behind, it's a nice gift to plan for this eventuality, even if it seems far off at the moment.

Re: The Future of the Vim Project

#14
post #8
post #6

Earlier quoted context omitted.

There’s no future to Vim without Bram. A merge of the two fork’s isn’t what Bram has wanted, but it’s the best way to keep Vim alive

I wouldn't be so dismissive. Vim is a marquee project, tons of hackers will want to contribute because it's cool or because they want to have that name on their CV.

Pretty much this. I'd like to take a crack at updating that vim.org page away from PHP5/MySQL.

Re: The Future of the Vim Project

#15
post #10
post #5

Earlier quoted context omitted.

Why not? vim and neovim have been separate for a long time already, wouldn't it work to continue like that?

If the project leads can agree to a shared vision - which frankly should be similar considering the scope of the projects - it's most likely better if they merge. Open Source projects never have enough resources and splitting them into 2 clone projects is generally not great. I know about competition but it's not like Vim/Neovim, programming text editor, is lacking in competition even without the other side of the fo…

>better if they merge

You and meitham are very focused on this, but it is very much an opinion and not a fact.

Re: The Future of the Vim Project

#16
post #6
post #5

Earlier quoted context omitted.

Why not? vim and neovim have been separate for a long time already, wouldn't it work to continue like that?

There’s no future to Vim without Bram. A merge of the two fork’s isn’t what Bram has wanted, but it’s the best way to keep Vim alive

No future for Vim without Bram? People said the same thing about Apple when Steve Jobs passed away. Turns out, as long as you have loyal users and competent people working, things can keep on chugging right along.

It seems a bit ridiculous to dismiss reunification when you don't even know what kind of compromises might be made to make it happen.

Re: The Future of the Vim Project

#20
post #15
post #10

Earlier quoted context omitted.

If the project leads can agree to a shared vision - which frankly should be similar considering the scope of the projects - it's most likely better if they merge. Open Source projects never have enough resources and splitting them into 2 clone projects is generally not great. I know about competition but it's not like Vim/Neovim, programming text editor, is lacking in competition even without the other side of the fo…

>better if they merge You and meitham are very focused on this, but it is very much an opinion and not a fact.

It is an opinion backed by watching Open Source projects for several decades.

Long lived forks are rarely good for an individual project. Frankly, the most successful forks I've seen unfortunately... kind of strangle off the original. Jenkins/Huson, LibreOffice/OpenOffice, MariaDB/MySQL, ConsoleZ/Console2/... Though there are cases where the original wins out: Emacs/XEmacs, etc.

Especially since it's not like Vim/Neovim are already lacking in features to implement, bugs to fix, ways to extend their architectures :-)

Post reply on HN