4 ms·

It is well explained in the blog article: https://bun.sh/blog/bun-v1.0#why-bun-exists https://bun.sh/blog/bun-v1.0#why-bun-exists This is extremely compelling

• afavour 3y ago
  That kind of speaks to my point, though: a number of the features listed there (e.g. test runner, .env file support, watch mode) have either been recently added to Node or will be soon (and are available today as experimental flags). The bundler stuff is certainly more compelling though the page doesn't specify what makes it better than esbuild except that it comes built-in... but that's where, for me, VC concerns raise their head. If I go all in on Bun bundler, what happens if the company switches their priority towards monetization and neglects the bundler? I'm going to have to unroll all the configuration work I will have done and go back to an external bundling library. And it's still not entirely clear what I gain!
  • fkyoureadthedoc 3y ago
    If it delivers on the promise of solving the require vs import module nonsense that would be enough for me. Maybe node copies that too, but that's also a win imo.
    • ShadowBanThis01 3y ago
      Does Deno suffer from that in the first place? I don't know what that issue even is, so I'm just asking.