[Kinrany]

For one-off scripts: every time.

So Deno is better at small scripts written in Typescript than Node. Then, the question becomes, if you're going to have Deno installed and if it works well enough to replace Node, why keep Node?

[willsmith72]

then you have to define "works well enough to replace Node"

i was excited about bun too, until v1's "drop-in node replacement"

that was in no way a drop-in node replacement. using that would be the fastest way to kill a business with its terrible bugs and rough edges.

i used to be really excited about deno, but now i think the tradeoffs aren't going to be worth it for mass adoption. i sometimes write servers in go. now that i have go installed, should i use it for all my servers? no, it's just another tool with different trade-offs. most times, node will suit my project better.