There is some focus on performance in Neovim (just ctrl-f for it here: https://github.com/neovim/neovim/wiki/Progress https://github.com/neovim/neovim/wiki/Prog

There is some focus on performance in Neovim (just ctrl-f for it here: https://github.com/neovim/neovim/wiki/Progress https://github.com/neovim/neovim/wiki/Progress). But more importantly, all IO is being ported to libuv, from the blocking calls that are currently being done. This obviously fits Javascript's IO model much better, as you don't have to fake an event loop in Javascript as this port is apparently doing - you just use the event loop the JS implementation provides. After that's done, I'd expect Neovim to work more smoothly as a JS port.