Live data from Hacker News

Oven: The Company Behind Bun

oven.sh

21–30 of 122 posts

Re: Oven: The Company Behind Bun

#21
post #8

I love these funny names. First time I introduced HomeBrew to my gf, she was all laughing at the funny terms: keg - Program binaries created from source bottle - Program binaries downloaded cellar - Directory where kegs / binaries are stored tap - git repository cask - macos native binary (not used in Linux)

Ok, but I'm not really looking to my package manager for entertainment. To me this jargon is just needlessly obtuse.

Re: Oven: The Company Behind Bun

#22
post #13
post #9

Earlier quoted context omitted.

I'm curious if it will be as fast after implementing some must have features like sourcemaps, minification, and tree shaking? Bun is definitely not production ready yet, but I'm keeping my eye on it for sure https://github.com/oven-sh/bun#not-implemented-yet

Sourcemaps are technically already implemented, but not for bundled dependencies. Initially, it was a 30% drop, but I made it use lots of SIMD and that compensated a lot. When you use Bun's runtime, it transpiles every file (including non-TypeScript files) and generates an in-memory sourcemap so that error messages have useful line/column numbers. Bun's fast startup time is very much in spite of things like this. Min…

I'm not looking to use Bun as a JS runner because all of my JS runs in the browser. The time and complexity of implementing these processes will increase build time. We will have to wait to see how it compares to existing tools for bundling and creating production code.

Re: Oven: The Company Behind Bun

#24
post #8

I love these funny names. First time I introduced HomeBrew to my gf, she was all laughing at the funny terms: keg - Program binaries created from source bottle - Program binaries downloaded cellar - Directory where kegs / binaries are stored tap - git repository cask - macos native binary (not used in Linux)

Ok, but I'm not really looking to my package manager for entertainment. To me this jargon is just needlessly obtuse.

I 100% agree. Cutesy names should end once the package name has been chosen. Package authors and contributors that overdo the thematic names should stick to writing fiction, not code.

Re: Oven: The Company Behind Bun

#27
post #16

Earlier quoted context omitted.

I'm curious about where all that performance comes from I know it uses the WebKit JS runtime instead of V8, which is super interesting. Does that cause a performance lift? Or is there some other secret sauce that pervades throughout Bun? Or is it just a matter of Jarred giving lots of attention to spot-optimizing the most important bottlenecks outside of the core runtime?

I suspect it’s the latter. I would guess V8 with a thin wrapper and a ton of effort from someone who cares about perf to port all the native goodies of node would get similar wins.

Good thing Cloudflare is open-sourcing their V8-based Workers runtime soon.

Re: Oven: The Company Behind Bun

#28

Why do they call it oven when you of in the cold food of out hot eat the food?

I feel like there’s two reasons why I don’t understand your comment at all. Either you made a pun somewhere in there that just went way over my head, or it’s way too early for me to be up. But I have no idea what „of in the cold food of out hot eat the food“ could mean
Post reply on HN