2 ms·
The difference is that io.js started as a fork, and Deno starts with the premise that node has many fundamental design flaws that can only be fixed with a rewri
by 29athrowaway 6y ago
The difference is that io.js started as a fork, and Deno starts with the premise that node has many fundamental design flaws that can only be fixed with a rewrite.
Perhaps some of the solutions in Deno can be ported to node, but others certainly can't. For example, there's so much dependency on node-gyp that it's unlikely it will ever go away.
By porting Deno's features to node you will be introducing so many backward compatibility issues and friction that it will be the same as porting your libraries and applications to Deno.