Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Future of the Vim Project

groups.google.com

Post reply on HN
Print view View original

81–90 of 376 posts

Re: The Future of the Vim Project

#81

Post by maxfurman »

kqr wrote: post #78
OskarS wrote: 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…

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?

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

Re: The Future of the Vim Project

#82

Post by School-Cotton »

suprjami wrote: post #34
djtango wrote: post #24

Earlier quoted context omitted.

I've not tried neovim mostly because I'm hopelessly loyal. curious what features were cut?

vim-cscope, which is the only reasonable way to read large C projects like the Linux kernel or BSD

What’s wrong with clangd via lsp?

Re: The Future of the Vim Project

#83

Post by sdfghswe »

petepete wrote: post #48
sdfghswe wrote: post #43

Earlier quoted context omitted.

3/4 seconds??? Something's wrong with your system, right?

They're milliseconds! I abbreviated the output, if you run the above command and check the file, at the top it says times in msec

Oh that's awesome actually.

Re: The Future of the Vim Project

#84

Post by praseodym »

maxfurman wrote: post #81
kqr wrote: post #78

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

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.

Re: The Future of the Vim Project

#85

Post by lowercased »

kqr wrote: post #78
OskarS wrote: 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…

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?

Being able to unsubscribe to a service, as someone else mentioned.

In social media world, posting some final "xyz has passed on. this account will be closing" or similar 'wrap up' activity is often useful.

Re: The Future of the Vim Project

#86

Post by chasd00 »

kqr wrote: post #78
OskarS wrote: 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…

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

#87

Post by evanriley »

praseodym wrote: post #84
maxfurman wrote: post #81

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.

Doesn't work for all services. Some services will, if unable to charge the card,send whatever amount to collections, and now they have to deal with that.

Re: The Future of the Vim Project

#88

Post by gkfasdfasdf »

enriquto wrote: post #45
fortunateregard wrote: post #17

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?

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

Neovim's language server integration is a killer feature that got me to switch.

Re: The Future of the Vim Project

#89

Post by bombcar »

0cf8612b2e1e wrote: post #80
bombcar wrote: post #31

Earlier quoted context omitted.

These types of mergers have occurred in the past and it usually is the dominant project adopting the use and feel of the features the other has different. Shells acting differently depending on how you call them, for example.

I am not sure how you reconcile some of the philosophical differences between the projects. One of the first objectives of NeoVIM was to dump code for obsolete computing platforms. A ton of legacy code was deliberately removed so as to streamline the project. If I recall correctly, one of the reasons the original async patch was ostensibly rejected was because it would rely on a C89(?) compiler. That was considered t…

It’s brutal to say it, but often you handle it by some of the people involved passing away.

Even if neovim basically takes over the older vim code wouldn’t disappear, so it would continue to exist for older platforms. People still keep certain versions of GCC around for similar reasons.

Or you abuse the preprocessor and automake.

Re: The Future of the Vim Project

#90

Post by Aissen »

0cf8612b2e1e wrote: post #80
bombcar wrote: post #31

Earlier quoted context omitted.

These types of mergers have occurred in the past and it usually is the dominant project adopting the use and feel of the features the other has different. Shells acting differently depending on how you call them, for example.

I am not sure how you reconcile some of the philosophical differences between the projects. One of the first objectives of NeoVIM was to dump code for obsolete computing platforms. A ton of legacy code was deliberately removed so as to streamline the project. If I recall correctly, one of the reasons the original async patch was ostensibly rejected was because it would rely on a C89(?) compiler. That was considered t…

async is water under the bridge since Vim 8, both Neovim and Vim have async apis. I foresee native LSP and everything-lua to be a bigger schism between Neovim and Vim.
Post reply on HN