>
> Both works well enough in Neovim. Though terminal UI is *now* part of
> the same executable (will be different one later), Python communicates
> through msgpack over a socket. This thing is obviously slower and in
> some cases people need to do optimizations, but most of time this is
> good enough. Also there are UIs other then terminal one and they all
> use pipes or sockets. Unlike for Python support I did not hear about
> problems with UI lags (though maybe because +python users are more
> common here then GUI users; on the other side UI authors did not raise
> issues regarding communication protocol speed so at least they think
> that nothing can be done to speed up, at most they know how to write
> their UI without it lagging).
>
> Also this is how most web applications work. UI is in browser. Backend
> is on server. And between them you have lots of routers which makes
> the whole thing much slower then if UI communicates with Neovim
> through msgpack. Still they work, using different hacks for different
> situations (from having most of the code on the frontend, only sending
> a few commands like “save {big blob}” to the backend once in a while,
> to requiring client have his own server with controlled latency).
>
Wait a minute ... I haven't tried neovim yet but I'm having my eye on it. If
neovim runs Python as an external process, then does Python have the 'vim'
module anymore ? Will Python be able to do 'import vim' and use its utilities
within its environment?
Please elaborate, thanks.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
