On 22 February 2014, ZyX <zyx.vim@gmail.com> wrote:
> > Except libuv is mainly intended for dealing with multiple
> > _network_ connections. Sure, this might come in handy at some (much
> > later) point, but Vim is not I/O-bound. Saying that libuv will
> > handle most of the platform differences seems a little naive.
>
> What?! `eix libuv` describes libuv as ???A new platform layer for
> Node???. Project own README says ???libuv is a multi-platform support
> library with a focus on asynchronous I/O.??? Where do you see
> ???network??? here? Also feature list from this README tells about 12
> features, and only two of them are about network.
As far as I can tell, libuv provides exactly what you need to write
node-style network servers, and to this day those are still the most
spectacular of its applications. Can you also use it for something else
if you ignore the network features? Sure, since it basically brings
libev to Windows, and libev is also supposedly a better libevent. :)
Now, _should_ you use libuv as a cross-platform glue if all you care
about is (local) IPC, rather than heavily concurrent I/O? Well, maybe
not.
/lcd
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Saturday, February 22, 2014
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment