I think Deno will eventually replace node in mindshare and deployment numbers. What percentage of nodejs packages run on both node and the browser and do you e

I think Deno will eventually replace node in mindshare and deployment numbers. What percentage of nodejs packages run on both node and the browser and do you expect that number to go up or down over time? If it goes up -- the percentage of node packages that run on deno also goes up. Code that runs in the browser is very valuable because it is an incredibly widely deployed user eyeball platform ... the browser _is_ the center of the javascript ecosystem -- and so there is already built-in pressure to migrate from node to deno -- especially if/when deno's browser matching api implementations become part of the compatibility testing matrix for a major browser vendor (like chrome or firefox) ... Deno will surf uphill on the ever rising value of browser compatibility until projects are actively weeding out any dependencies which "run only on node". Even given the huge dependency graphs of node applications -- you don't really have to replace that many high level dependencies before you've migrated yourself to deno ... -- and you will experience incremental benefit for partial steps along the way as you do ...