How to handle de facto replacements

[jneidel]

Sometimes a fork or a reimagining of a project takes off and de facto replaces the original. To new users you would always recommend the replacement. The old one is not deprecated or archived, but is not keeping up with the times.

Examples:

• screen -> tmux
• vi -> vim -> neovim
• youtube-dl -> yt-dlp
• sxiv -> nsxiv
• mutt -> neomutt

This list having the old entires at the top gives more room to the old, replaced version.

[vitaly-zdanevich]

Vim is not replaced, they have commits everyday

[jneidel]

Vim is not replaced, they have commits everyday

youtube-dl is also still being updated. Such is the nature of forks.

But there is a difference between maintenance and active expansion.

I would never recommend somebody to start with vim > neovim. Especially if they come from an IDE. Vimscript is dreadful, Lazy, LSP and the plugin ecosystem more generally are already worth going with neovim.

I don't think dropping vim, in this example, from the list is the best way. But there could be a note that most users will want to go with neovim.