3 ms·
It is the same conference! They have rebranded this year to Neovim conf [0]. The conference however is not exclusive to Neovim content. [0]: https://www.neovim
by TymekDev 4y ago
It is the same conference! They have rebranded this year to Neovim conf [0]. The conference however is not exclusive to Neovim content.
[0]: https://www.neovimconf.live/rebranding-rationale https://www.neovimconf.live/rebranding-rationale
- capableweb 4y agoThat's confusing to say, at best. If it's called VimConf, I could understand including content from anything vim related, even vi or neovim stuff (or from the other forks/variations/bases). But if it's called NeovimConf, I wouldn't expect that to include the entire Vi ecosystem.
- ehutch79 4y agoAccording to the FAQs they rebranded because all the traditional vim people complained about too much neovim content. Apparently the neovim people are more chill about it.
- rhaway84773 4y agoMost VIM stuff works in NeoVIM as well. NeoVIM exclusive stuff doesn’t work as well or at all in VIM.
- nerdponx 4y agoThat will be changing soon. Vim 9 has a new version of Vimscript (called Vim9script) which Neovim doesn't support, and its APIs for things like async jobs are also different. However Vimscript itself will probably remain a common denominator for many years to come.
- cbm-vic-20 4y agoTJ DeVries (one of the Neovim contributors, and a frequent streamer) was working on some sort of vim9 translation support for Neovim. Seems more like a side project rather than something that will be built into Neovim, though. https://github.com/tjdevries/vim9jit https://github.com/tjdevries/vim9jit
- User23 4y agoThe neovim people are even chill about Emacs evil-mode content.