Bun is exciting
Bun is exciting.
But Bun’s “all-in-one”approach has many risks and downsides:
🚫 Bun will often lag behind changes to the separate tools it replaces. When JS tools innovate, will Bun be able to quickly support something similar?
🚫 If it’s buggy or insufficient, Bun is harder to replace than separate tools.
🚫 Can I still mix and match tools to select a “best-of-breed” stack?
🚫 Higher risk - The tool chain is reliant on one team instead of many. What if Bun’s small team burns out or runs out of funding? Replacing Bun quickly may be hard.
🚫 Lack of ecosystem. Will cloud providers support Bun? Will a community form around Bun to provide extensions and support? Are the docs sufficient?
🚫 Will Bun honor JS standards or seek to “extend and extinguish”? The latter is a common approach that makes products sticky, but also breaks compatibility. Bun already has some non-standard behaviors.
🚫 Can one small team support something this complex long term?
To be clear, I’m rooting for Bun. But what they’re trying to accomplish is hard and risky. Will it work?