#libuv — Public Fediverse posts

@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)

@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)

@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)

@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)

@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)

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.

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.

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.

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.

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.

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

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

https://habr.com/ru/articles/840108/

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

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

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

https://habr.com/ru/articles/840108/

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

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

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

https://habr.com/ru/articles/840108/

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

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

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

https://habr.com/ru/articles/830644/

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

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

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

https://habr.com/ru/articles/830644/

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

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

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

https://habr.com/ru/articles/830644/

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

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:​

https://github.com/nodejs/node/issues/53051

#nodejs #linux #libuv

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:​

https://github.com/nodejs/node/issues/53051

#nodejs #linux #libuv

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:​

https://github.com/nodejs/node/issues/53051

#nodejs #linux #libuv

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:​

https://github.com/nodejs/node/issues/53051

#nodejs #linux #libuv

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:​

https://github.com/nodejs/node/issues/53051

#nodejs #linux #libuv

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: https://github.com/websockets/ws/issues/2148

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: https://github.com/websockets/ws/issues/2148

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: https://github.com/websockets/ws/issues/2148

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: https://github.com/websockets/ws/issues/2148

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: https://github.com/websockets/ws/issues/2148

#libuv Adds #IO_uring Support For ~8x Throughput Boost

https://www.phoronix.com/news/libuv-io-uring

Original tweet : https://twitter.com/phoronix/status/1648333901176135682

#libuv Adds #IO_uring Support For ~8x Throughput Boost

https://www.phoronix.com/news/libuv-io-uring

Original tweet : https://twitter.com/phoronix/status/1648333901176135682

#libuv Adds #IO_uring Support For ~8x Throughput Boost

https://www.phoronix.com/news/libuv-io-uring

Original tweet : https://twitter.com/phoronix/status/1648333901176135682

#libuv Adds #IO_uring Support For ~8x Throughput Boost

https://www.phoronix.com/news/libuv-io-uring

Original tweet : https://twitter.com/phoronix/status/1648333901176135682

#libuv Adds #IO_uring Support For ~8x Throughput Boost

https://www.phoronix.com/news/libuv-io-uring

Original tweet : https://twitter.com/phoronix/status/1648333901176135682

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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!

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