3 ms·
Although expected, it is a little clunky/slow to use. Fun to play around with nonetheless, but I wonder whether an Emscripten port of Neovim would be a little s
by bananaoomarang 12y ago
Although expected, it is a little clunky/slow to use. Fun to play around with nonetheless, but I wonder whether an Emscripten port of Neovim would be a little sprightlier.
- teacup50 12y agoWhy would a port of a more unstable Vim with hacky IPC-based plugin mechanism be "sprightlier"? Dropping support for operating systems and reformatting the code doesn't make it run faster.
- ehsanu1 12y agoThere 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.