deno

No real support, just a placeholder on their roadmap: https://github.com/denoland/deno/issues/1739

> How do we know this? Looking at the source code [0] for Deno HTTP server, they spawn at least one thread for the server to listen and handle requests, before they are sent through a MPSC channel to the thread running the Isolate. [0]: https://github.com/denoland/deno/blob/07213dec94398aab687afd...

I was curious about what all shares the same web cache, exactly -- basically, can a random script poison a cache something like `deno_install` might use -- and didn't find that clearly documented. The answer is here: https://github.com/denoland/deno/blob/716005a0d4afd1042fa75d... So - value of `deno run --location=` - value of `deno run --config=`, also automatic probing - path to main script file, or for `deno eval`, current directory

Node API will be supported sometime soon https://github.com/denoland/deno/pull/13633

It's not a guaranteed guarantee as far as I can understand. Or such bugreports would make no sense: https://github.com/denoland/deno/issues/15020

And hyper, for their native HTTP extension (for http2). https://github.com/denoland/deno/blob/main/ext/http/lib.rs#L...

Out of curiosity I went through that whole pr discussion and I guess a maintainer posted a performance comparison, but Im not sure what numbers I'm supposed to be comparing. Do you know? https://github.com/denoland/deno/pull/9722#pullrequestreview...

Back when I was monitoring deno's progress, I came across this PR by Aaron O'Mullan that improved deno's perf significantly: https://github.com/denoland/deno/commit/3d2e05dc7b6735fe0b81... I believe they joined deno shortly after. So, I guess it does happen.

I think realms are the future in this direction. https://github.com/denoland/deno/issues/13239

> New experimental HTTP server API > Our benchmarks show a 4x improvement in hello-world request per second performance compared to Node.js and a 3x improvement compared to our existing web server. What the heck was wrong with the previous implementation? :P https://github.com/denoland/deno/pull/15405 I think this is the PR for it though. Unless the performance benefits are from something else in https://github.com/denoland/deno/releases/tag/v1.25.0

You overestimate many of these difficulties. The --compat mode can already run quite a bit of the node ecosystem, including programs like npm. Imports don't need to be written in typescript. They could have manually written type definitions (which is how people using typescript in the node ecosystem already handle this), and packages without type definitions will have the imports typed as `any`. Sure that makes them a bit annoying to handle especially in strict mode, but it entirely possible to use such packages. Deno is actually working on adding the native node API (https://github.com/denoland/deno/pull/13633), so the website was a bit overoptimistic when saying "Deno will never support Node plugins". However it is possible for some plugins to be incompatible still, for example if they try to use node internals rather than just the API,

> The "npm:" import does not appear to have even started development, although it has been planned for a long time: https://github.com/denoland/deno/issues/13703 The development is well under way, we expect to ship first iteration of this feature in the next release (v1.25) in the coming weeks.