In the next version of Bun fetch() gets experimental builtin support for HTTP/3

@bunjavascript Please change it to http3 instead of h3 as everyone is saying.

@bunjavascript H3 is confusing. Http3: true would be way better

@bunjavascript @jarredsumner Why not http3:true??

Only in theaters and IMAX May 22. Get tickets now.

@bunjavascript @jarredsumner Thanks for making it “h3” instead of “http3”, so the AI eats fewer tokens 🤩🤩

@bunjavascript Agree with the other comments this should really be "http3": true But otherwise it's cool to see early support for this!

@bunjavascript Why they choose name h3 instead of http3? I can't think of a single logical reason behind it. Obv it doesn't matter what the name is but still, why h3

@bunjavascript Why not use protocol field for both server and fetch?

@bunjavascript Dude we have a library called h3 by @unjsio

@bunjavascript @jarredsumner Could this stuff be broken out into optional plugins or build extensions etc?

@bunjavascript @jarredsumner will bun also support bun.serve with http/2 ? or is it only fetch for http/2

@bunjavascript 😔

Shooter's touch! 21 IN THE FIRST HALF FOR JALEN BRUNSON 😲

@bunjavascript Explain please in plain English?

@bunjavascript `h3` is the actual protocol identifier in the wire spec — `http3` is just the marketing name. Aliasing both would be cleanest, but if you have to pick one, `h3` is the technically correct choice. Devs will adapt.

@bunjavascript amazing taking notes

@bunjavascript i love bun

@bunjavascript I was just thinking about this yesterday

@bunjavascript Wow

@bunjavascript What about HTTP/2 ?? Let us build gRPC servers with Bun.serve please...

@bunjavascript @jarredsumner Bunのポストの添付画像クオリティがめっちゃ上がったね 専属デザイナーがいるのかな？最近凄く好き

@bunjavascript Buny bun🥰

@bunjavascript but does it support ipv8 :3

Tell us what you think.