#tokiors — Public Fediverse posts

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.