1. Standard library: Deno has so much better standard library, support for web standards, promises instead of callback, and need to reach out to third party modules lot less
2. Performance: Deno is focusing a lot on performance and it faster than node
3. Package management: No more gigabytes of node_modules, They just have URLs which are simpler to use
4. Versioned std library:node's standard library is packaged but for deno you can use different std library than deno version.
Whats worse:
1. Ecosystem: There are lot less packages for deno but Deno team is working on npm packages support. So all/most npm packages will work in deno
2. Deployment target: Deno has deno deploy but that pretty much it.
1. Standard library: Deno has so much better standard library, support for web standards, promises instead of callback, and need to reach out to third party modules lot less
2. Performance: Deno is focusing a lot on performance and it faster than node
3. Package management: No more gigabytes of node_modules, They just have URLs which are simpler to use
4. Versioned std library:node's standard library is packaged but for deno you can use different std library than deno version.
Whats worse:
1. Ecosystem: There are lot less packages for deno but Deno team is working on npm packages support. So all/most npm packages will work in deno
2. Deployment target: Deno has deno deploy but that pretty much it.