The Deno Company
A lot of people seem to think the difference between Deno and Node is trivial, but having actually used Deno, I think they&#x27;re wrong.  Here&#x27;s why:<p>- Typescript as a first class citizen<p>- An actual `window` global with familiar browser APIs<p>- Sandboxing w&#x2F; permissions<p>- URL-based imports (no need for NPM)<p>- Bundling into self-contained binaries<p>- Things like top-level-await which Node.js still treats as experimental.<p>- Better-designed APIs than the Node standard lib (esp. when it comes to promises instead of callbacks)<p>To me, those aren&#x27;t just minor details.  This has the potential to create a new epoch in server-size JavaScript.