Re:The Future of the Vim Project
by OJFord on Thursday August 10, 2023 @08:01AM
(#37075069)
Well, why should I? I don't need a reason not to do everything, by default I'm not doing things, it's changing from status quo that requires a reason.
[ Parent
| on HN ]
It's easier to maintain one codebase than to maintain two forks.
If development of vim dropped and neovim was nominated as its successor, I'd think most vim users would be just fine.
Yes, if vim were unmaintained I would switch, that would be a reason to change. But it's not, or at very least hasn't been, so I haven't, that hasn't been a reason to.
Re:The Future of the Vim Project
by halostatue on Thursday August 10, 2023 @09:52AM
(#37076176)
Not those of us who gvim/MacVim.
Give a real alternative to those instead of the many quarter-implemented GUI shells that are really no better than running Electron, and the switch might be able to happen.
Re:The Future of the Vim Project
by yjftsjthsd-h on Thursday August 10, 2023 @11:00AM
(#37077026)
> It's easier to maintain one codebase than to maintain two forks.
Not necessarily; if the two codebases are maintained by groups of people with incompatible ideas about how the code should work and what it should do, then keeping things separate is much easier.
> If development of vim dropped and neovim was nominated as its successor, I'd think most vim users would be just fine.
Agreed; they don't diverge that much from an end-user's perspective.