> Node is almost perfectly matched to the "Oops, well, too late now" design ethos of JavaScript itself. Anything even remotely successful has to commit to its

> Node is almost perfectly matched to the "Oops, well, too late now" design ethos of JavaScript itself. Anything even remotely successful has to commit to its previous choices, even when they were unfortunate (did anybody say C++?). One of the reasons why Node had the impact it had was that it used plain JS and committed to supporting the standard language. I myself prefer writing in statically-typed languages, but the JS direction is frankly commendable; ES6 looks nothing like OG JS, and the fact you can run basically the same code on the browser and on node is a massive bonus. With that said, I hope Deno succeeds as well, having more choices is a good problem to have!