Boost.Asio VS libuv

Indeed looks like it, strand_executor_service.hpp is using a Mutex internally (otherwise it wouldn't make sense to me).

as a side note, Asio is also released as an independent library without the boost stuff https://think-async.com/Asio/

Now that vinniefalco is going to kill off the asio standalone (see deprecate standalone ) and only support boost what would people then recommend to switch over to.

The ASIO framework can be found at https://think-async.com/Asio/ and the relevant license for its use is included in the GitHub repository in the Vendor/licenses directory.

The library is found at https://think-async.com/Asio/.

Asio Extracted from the much bigger Boost C++ library, it's apparently a really good networking library. As a bonus it also handles async / threads. Here's a really good video tutorial by OneLoneCoder

Yes: https://github.com/chriskohlhoff/asio/blob/master/asio/include/asio/coroutine.hpp

Here's the main contributor to Asio. I looked at Asio's repository and this was the first guy.

The event loop is the core mechanism in Node.js that enables non-blocking I/O operations. Despite Node.js being single-threaded by default, the event loop allows it to perform asynchronous operations by offloading tasks to the system kernel or Libuv's thread pool. This makes Node.js highly efficient for I/O-heavy applications, such as web servers and APIs.

I know good naming is hard, and there are an awful lot of project names that clash, but naming a project uv is unfortunate due to the ubiquitous nature of libuv

https://libuv.org/

Almost everyone running Node in a machine with multiple cores is using multithreading.

Node is multithreaded by default. I believe the default setting is using 4 threads. Most of Node is written in C++.

The JS code written by end users is single threaded (most of it at least) but IO etc is all executed with libuv.

https://libuv.org/

OrbStack is by far some of the best software I've encountered on Mac, but unfortunately I have difficulty convincing my employer to pay for a commercial license, and with my sparse Docker usage, I'm confined to using it only for personal/hobby usage.

What's amazing is it fixes an (almost) show stopper bug when using libuv (or software that uses it like CMake) with Rosetta 2 [1], with the bug present on all Docker/VMs I've tried except OrbStack. It just seems to get everything right.

[1]: https://github.com/libuv/libuv/issues/4279

I wound up on a different team with pre-existing Python code so temporarily shelved my use of Go for a bit, and we used Sanic (an async Python framework built on top of the excellent uvloop & libuv that also powers Node.js) to build some APIs for live channel management & operations. We hand-wrote our OpenAPI and used it to generate documentation and a CLI, which was an improvement over what was there (or not) before. Other teams used the OpenAPI document to generate SDKs to interact with our service.