Earlier quoted context omitted.
What's the target level of compatibility with existing npm modules? 100%? Some lower percentile? Hate to carry forward baggage of past design choices, but likely essential to really get widespread adoption. I'd definitely start using Bun for my projects today (non-production), if it works seamlessly with existing packages.
I suppose a compatibility shim for features that should not go into the new core could work. It would have a performance cost, but as long as this cost is limited to some deprecated APIs it would be OK.
Bun 0.3
31–40 of 64 posts
Re: Bun 0.3
#32Re: Bun 0.3
#33I work on Bun happy to answer any questions or feedback
What's the target level of compatibility with existing npm modules? 100%? Some lower percentile? Hate to carry forward baggage of past design choices, but likely essential to really get widespread adoption. I'd definitely start using Bun for my projects today (non-production), if it works seamlessly with existing packages.
Basically everything that doesn’t rely on node’s internal “bindings” C++ stuff should eventually be supported
Re: Bun 0.3
#34I work on Bun happy to answer any questions or feedback
Re: Bun 0.3
#35I work on Bun happy to answer any questions or feedback
Were there any organizational or policy changes after the "9 month grind" [0] tweet? Or is this still the policy of the bun/oven org?
Re: Bun 0.3
#36Earlier quoted context omitted.
FWIW this similarly-trivial "Hello world" benchmark shows Bun's lead at ~25% faster than Deno at the moment, which doesn't seem insurmountable. https://github.com/denosaurs/bench
Those benchmarks are measuring the speed of the tool used to run the benchmark, not the http servers. Take them with a pack of salt.
Re: Bun 0.3
#37I like this tech "fights" (evolutions). Even if bun will not overtake node, it will make node better. We see this many times with other projects (js/coffeescript/typescript/..., php/HHVM/HPHPc, webpack/vite/...)
Re: Bun 0.3
#38I like this tech "fights" (evolutions). Even if bun will not overtake node, it will make node better. We see this many times with other projects (js/coffeescript/typescript/..., php/HHVM/HPHPc, webpack/vite/...)
I would also mention io.js in Node's lifetime and Merb in Rails’
Re: Bun 0.3
#39Re: Bun 0.3
#40I work on Bun happy to answer any questions or feedback
Bun seems really cool! I had a question about this part: > Bun now works in more Linux environments, including Amazon Linux 2 and builds for Vercel and Cloudflare Pages. (Previously, you might have seen errors like: "version 'GLIBC_2.29' not found") How would building for Vercel and CF pages work? Like normal but installing the relevant build tools using bun?
Right now you’d need to download it via curl https://bun.sh/install | bash
But we need to make that better