Bun 0.3 • Hacker News Board

Re: Bun 0.3

#21

Post by adam_arthur » Wed, Dec 07, 2022, 6:29 PM UTC

progx wrote: post #4

I 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/...)

Happened with node via io.js back in the day too

Re: Bun 0.3

#22

Post by Jarred » Wed, Dec 07, 2022, 6:31 PM UTC

christophilus wrote: post #17

Jarred wrote: post #13

Earlier quoted context omitted.

The “tls” module is on our list of node core modules to implement, somewhere near the top

Not that I want to cause scope creep, but it would be amazing to have something like the certmagic library (the Caddy team’s automatic TLS Go library) without having to reach for a 3rd party.

I would love for us to do this builtin to Bun.serve()

No idea about timeline but something we are thinking about

Re: Bun 0.3

#23

Post by gcoguiec » Wed, Dec 07, 2022, 6:31 PM UTC

progx wrote: post #4

I 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

#24

Post by panzerboiler » Wed, Dec 07, 2022, 6:34 PM UTC

CharlesW wrote: post #15

philippz wrote: post #7

Earlier quoted context omitted.

https://medium.com/deno-the-complete-reference/hello-world-p...

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

#25

Post by adam_arthur » Wed, Dec 07, 2022, 6:42 PM UTC

I'm surprised JSC doesn't get more press. Lots of news/articles about V8, but seems JSC has eclipsed it on perf by some metrics.

Overall though, Bun honestly looks like it has a shot to supplant Node if npm package compatibility reaches a sufficient level. Or at least encourage Node to work much harder on perf. Deno feels a bit too esoteric/theoretical in its approach, vs Bun which looks to be much more focused on ease of use

Re: Bun 0.3

#26

Post by adam_arthur » Wed, Dec 07, 2022, 6:53 PM UTC

Jarred wrote: post #12

I 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.

Re: Bun 0.3

#27

Post by _hypx » Wed, Dec 07, 2022, 6:58 PM UTC

xchkr1337 wrote: post #6

I don't see any reason to use this over Deno.

The more options the better.

Re: Bun 0.3

#28

Post by nesarkvechnep » Wed, Dec 07, 2022, 6:59 PM UTC

progx wrote: post #4

I 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/...)

Also Elixir made Erlang better.

Re: Bun 0.3

#29

Post by dstaley » Wed, Dec 07, 2022, 7:04 PM UTC

johnnypangs wrote: post #19

Jarred wrote: post #12

I 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?

Additionally, I'd love to see the PR where this change was implemented. I've been trying to convince Zola, a static site generator written in Rust, to support older versions of GLIBC.

Re: Bun 0.3

#30

Post by nine_k » Wed, Dec 07, 2022, 7:04 PM UTC

adam_arthur wrote: post #26

Jarred wrote: post #12

I 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.

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.