If Node & Deno where to merge, what should the good parts?

Regardless of who merges into who, if there would be a merge which parts should be kept?Spontaneously I would say:- ESM modules- Top level await- secure runtime- browser apimaybe also:- typescript?I don't include dropping package.json because I don't see how having import { serve } from “https://deno.land/std@0.50.0/http/server.ts"; spread across the whole app is better than in 1 place (of course we could do it in a packageIndex.js and import all stuff there and have it DRY, but then package.json does that already, right?)

Submitted June 03, 2020 at 12:45PM by sergiosbox