2 ms·
> Thus leading to the question of why even bother with Deno? 1. Native support for TypeScript. 2. Better built-in APIs. 3. Security model. 4. Easy package m
by paulddraper 3y ago
> Thus leading to the question of why even bother with Deno?
1. Native support for TypeScript.
2. Better built-in APIs.
3. Security model.
4. Easy package management.
Node.js is closing the gap. E.g. top-level await, fetch() API, Permissions.
I believe Node.js will follow Deno and implement more and more features. Sort of a npm/yarn situation.
It's cool to see what Deno does, but I don't think you will be left out by sticking with Node.js.