[voat]

People underestimate the node compatibility that Deno offers. I think the compat env variable will do a lot of adoption. Maybe a denon command or something could enable it automatically? Idk.

[efilife]

The deno compatibility with node has been a lie for me. I tried to port a simple project (100-200 LOC) to deno and it took me an hour which should have been 5-10 minutes. It didn't support some of node's methods and if it did, it was completely undocumented. Had to install basic functionality from some obscure URLS. Onxe it came to porting my test suite I just gave up. The problem was CJS -> ESM transition that was way more painful than I anticipated it to be. And definitely not as simple as deno's docs make it to be. Couldn't just port the whole library

[CuriouslyC]

Honestly, I was bullish on Deno back in the day, but I don't see why I'd use it over Bun now.

[jitl]

Less segfault, improved security / capability model

[pjmlp]

I have yet no reason to fight IT and architects for having anything besides node on CI/CD pipelines and base images for containers.