4 ms·

I hope we figure out a better way to deal with the mountain of dead (and just plain bad) packages on NPM. Not carrying this legacy always sounded like a plus to

I hope we figure out a better way to deal with the mountain of dead (and just plain bad) packages on NPM. Not carrying this legacy always sounded like a plus to me, but I haven't used Deno in production yet. It's also interesting to note how the tone changes after receiving funding. May just be a coincidence, but this looks like a reactionary jab back at Bun, which is barely out of the gate.

benatkin 4y ago
The first individual investor in the funding announcement is Nat Friedman, who defended ICE while at GitHub. I was one of many who signed the petition and cancelled my GitHub Pro account. Node is still a community project, since the creation of the Node.js Foundation. I feel like switching to Deno would be going backwards. https://www.theverge.com/2019/10/9/20906213/github-ice-microsoft-software-email-contract-immigration-nonprofit-donation https://www.theverge.com/2019/10/9/20906213/github-ice-micro...
- andrew_ 4y ago
  This seems unrelated to the parent and a bit of soapboxing.
  - zemo 4y ago
    can't say that I agree, it's in response to this: > It's also interesting to note how the tone changes after receiving funding. seems on-topic to me.
qbasic_forever 4y ago
Deno has had a node compatibility flag for a while now, and quite a few node packages have worked flawlessly. For anyone who has been using deno for some time this is not a big surprise to see smoother npm import support. I think all the people saying this is such a giant, game-changing big deal or that deno has changed, blah blah haven't actually been using it...