4 ms·
As someone maintaining a project with its own event loop: don't do it in larger projects. The problem is that you'll start having dependencies on external libr
by eqvinox 3y ago
As someone maintaining a project with its own event loop: don't do it in larger projects.
The problem is that you'll start having dependencies on external libraries. And when those then need event loop integration, things get messy. We've introduced bugs before, caused by subtle differences in semantics. (Like: does write imply read? Are events disarmed while running? What about errors?)
If the lib and event loop are reasonably popular, someone else probably has integrated them before. Or the lib supports the event loop natively (or uses libverto.) Either saves you some trouble.
Also: please add libverto support for your event loop :)
https://github.com/latchset/libverto https://github.com/latchset/libverto
- GoblinSlayer 3y agoThe interface looks like verto is linux first design, like git. But what's the point? Just implement epoll like Illumos did. Also allocation heavy and apparently can't use deno-style loop.