home.social

#libuv — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #libuv, aggregated by home.social.

fetched live
  1. ⚡ Slint 1.17 gives the Node.js binding a big upgrade.

    's event loop now hooks straight into on Linux & macOS: UI events are handled instantly, and idle apps drop to 0% CPU (no more 16 ms polling).

    Full deep dive 👇
    slint.dev/blog/slint-and-the-n

  2. @mdhughes since when and how so? all I'm aware of is #swish, which runs in a single OS thread and uses #libuv for async io (same as Node.js I believe)

  3. At a very basic core level, a comparison between @deno_land 2.0 and @nodejs could probably be summarised as:

    - JS-runtime: Both uses V8
    - Asynchronous I/O: Node.js uses #libuv, Deno uses #tokiors
    - Native code: Node.js uses C++, Deno uses Rust

    So essentially it boils down to libuv vs tokio and C++ vs rust

    If one ignore everything else about Node.js and Deno, the winner is clear to me.

  4. Красно-черные сигналы в node.js

    Что происходит, когда мы отправляем сигнал приложению на node.js? Когда вызываются обработчики? А где хранятся? Во всем этом мы разберемся в данной статье, начиная от пользовательского кода на javascript и до встречи с операционной системой.

    habr.com/ru/articles/840108/

    #javascript #nodejs #libuv #красночерное_дерево #epoll #linux #сигналы

  5. Куча таймеров в node.js

    А знаете ли вы, как на самом деле работают таймеры в node.js? В этой статье мы разберемся, как хранятся таймеры, когда запускаются и как в целом все работает вплоть до системных вызовов.

    habr.com/ru/articles/830644/

    #javascript #nodejs #libuv #куча #очередь #epoll #linux #таймеры

  6. Funsies: node-gyp is broken on latest kernel.

    Likely some other libuv stuff as well. In case you're experiencing more weirdness than usual, consider a downgrade :blobcatthumbsup:​

    github.com/nodejs/node/issues/

    #nodejs #linux #libuv

  7. Does anyone know what a #libuv / #nodejs uv_write_cb status of -89 means? I'm seeing:

    STREAM 18901: do read
    STREAM 18901: onWriteComplete -89 undefined
    Error: ERR_STREAM_DESTROYED: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed

    In my logs with NODE_DEBUG=stream enabled, full stacktrace at: github.com/websockets/ws/issue

  8. The biggest complaint people have about is the filesystem api is inconsistent.

    This is absolutely true, and sockets.sh completely replaces it.

    Our file system api should be instantly familiar to developers, it uses under the hood😎

  9. WOOOOOOO #cjdns finally runs for more than 30 seconds with the timer infrastructure rewritten with #Rust / #Tokio rather than #Libuv.
    😅

  10. Oh @rysiek I think you know me long enough to know I am never excited about package management :) It seriously didn't cross my mind at all when I was writing this (#npm who?:) @charlag

    #libuv ftw!