Thread

On caring for user data: NeoVim caused Vim undo files to be deleted

384 points · 346 comments · jandeboevrie

dlisboa · 1790522895 · focus · HN ↗
> the attitude that just because something is a persistent file on your filesystem that contains data that you might want is no reason for their program not to delete it meant they had no concept of a duty of care to their users.
That's the wrong way to look at it. NeoVIM has a different concept of care for their users. They're optimizing for another kind of care, more in line with modern expectations, which VIM did not care about (hence the fork).
It's not better or worse, just different.
This same article could've been written about how VIM has no native LSP integration or autocomplete and they don't have duty or care for their users.
1. lokar · 1790526257 · focus · HN ↗
  All they had to do was pick a different file name
  1. dlisboa · 1790526585 · focus · HN ↗
    True. But it’s not like they planned some vengeance against the VIM backup file.
    People are making it sound like this is a huge company with a product and not a grouping of curious people with a couple hours of free time on a Sunday.
    Most likely they never thought about it, then it broke, then it was not impactful enough to fix on their free time compared to other stuff.
    jeremyjh · 1790527012 · focus · HN ↗
    They knew about it in advance. They decided people shouldn't care about that data.
    <a href="https://github.com/neovim/neovim/pull/13973#issuecomment-789262094" rel="nofollow">https://github.com/neovim/neovim/pull/13973#issuecomment-789...

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.