David Chisnall, a computer scientist, highlighted the importance of Vim's persistent undo feature, which he has used for approximately 20 years. This feature allows users to recover deleted content or revert changes made days or weeks prior, even after closing and reopening files or system reboots. It adheres to Raskin's First Law, which states that a program should not harm a user's data.
Upon trying Neovim, a fork of Vim, Chisnall discovered that its undo functionality was broken. Neovim had altered the format of persistent undo files, deleted existing Vim undo files, and replaced them with a format that Vim could not read. This action led to the loss of his undo history in both Neovim and subsequently in Vim.
When Chisnall reported the issue, he was informed by Neovim developers that the persistent undo format was unstable and users should not depend on data preservation within a feature explicitly named 'persistent undo.' This response, coupled with the data loss, led Chisnall to conclude that Neovim's developers lacked a concept of duty of care to their users, causing him to cease using the editor.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
A computer scientist criticized Neovim for deleting and replacing Vim's persistent undo files with an incompatible format, leading to data loss. This action and the developers' response were seen as a failure to uphold a duty of care to users.