A breakdown of the history of Deno, the emergence of Bun, and a reaction to the Cloudflare acquisition by a developer who went all-in on Deno years ago.
  • bitfucker@programming.dev
    2·
    14 hours ago

    IMHO, the problem with deno was trying to be too different. That is it. De facto standard tooling and existing knowledge about server side JS/TS goes out of the windows. Don’t get me wrong, it does force NodeJS to be more innovative but those friction is too big of a cost compared to myriad of example using NodeJS. So when Bun is trying to be 1-1 drop in replacement with added frail, everyone loves that