Live data from Hacker News

Oven: The Company Behind Bun

oven.sh

41–50 of 122 posts

Re: Oven: The Company Behind Bun

#41

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

It’s a reference to a meme:

https://knowyourmeme.com/memes/why-do-they-call-it-oven

Re: Oven: The Company Behind Bun

#42
My moneys on Just-JS.

It’s consistently in the top 5 fastest web framework (beating out Rust, etc).

Just-JS is already faster than Bun.

Additionally, JSCore appears to be a significant reason why Bun is faster than NodeJS (V8). Just-JS is investigating switching to JSCore as well - which will only extend its lead.

https://github.com/just-js/just

https://www.techempower.com/benchmarks/#section=data-r21

https://twitter.com/justjs14/status/1560741923106725889#m

https://twitter.com/justjs14/status/1557856790897106944#m

Re: Oven: The Company Behind Bun

#43
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.

hm quite a sour take. I find that the names actually are reflective of an actual storage process so they fulfill both the playfulness and the natural naming.

Re: Oven: The Company Behind Bun

#44

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

It's a reference to a meme, which is intentionally nonsense.

Re: Oven: The Company Behind Bun

#45

It's an incredible achievement, though I worry about the use of an unproven language (Zig) that lacks memory safety by design. JavaScript runtimes, especially those with JITs, have been plagued by vulnerabilities from memory safety, type confusion, and data races. Node.js, despite being based on V8, is still susceptible independently of V8 and introduces its own vulnerabilities. It's not sufficient for the runtime to…

Worth clarifying that Bun isn't a from-scratch JS runtime, it's a wrapper around JavaScriptCore (WebKit's JS engine), like Node is around V8

As you say, there's still plenty of room for vulnerabilities in the parts it does implement, and Zig isn't strictly memory-safe. However, Zig has lots of modern features like optional-types that help quite a bit with avoiding memory errors: https://www.scattered-thoughts.net/writing/how-safe-is-zig/

Which is to say your question is definitely valid, but there are also reasons to think this isn't as huge a concern as it might seem

Re: Oven: The Company Behind Bun

#46

It's an incredible achievement, though I worry about the use of an unproven language (Zig) that lacks memory safety by design. JavaScript runtimes, especially those with JITs, have been plagued by vulnerabilities from memory safety, type confusion, and data races. Node.js, despite being based on V8, is still susceptible independently of V8 and introduces its own vulnerabilities. It's not sufficient for the runtime to…

I am fairly confident that Zig does not lack memory safety by design; from what I understand, the language as a whole isn't even finished, and the memory safety design isn't like a GC'd language or like Rust, so people assume there isn't memory safety when in reality it is at least partially implemented.

I'm afraid "partially implemented" memory safety is also widely known in the offensive security industry as "not memory safe". Many people have fooled themselves into thinking there is a gradient with safer C++ abstractions, libraries in C, custom allocators, static analyzers, valgrind, etc.

Re: Oven: The Company Behind Bun

#47

Earlier quoted context omitted.

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.

"keg" and "bottle" are cutesy? well, to see the exact opposite of "cutesy", please fork homebrew and give all of those things GUIDs for names, including all the packages a user could install; you'll soon see why the names chosen are quite acceptable, indeed.

[deleted]

Re: Oven: The Company Behind Bun

#48
finally, a tech company with a cute design aesthetic :D i'm so happy to see a cute little bun in an oven instead of standard tech company imagery. i've never used bun and don't have great reason to, but it makes me hopeful to see.

Re: Oven: The Company Behind Bun

#49

Are Bun and Deno in direct competition or do these projects address different markets?

They are roughly in competition, though Deno made the decision early on to largely split itself from the ecosystem and existing conventions of Node (and an enormous body of existing JavaScript packages on npm), whereas Bun did not. Bun, AFAIK, aims to be compatible with Node and existing the npm ecosystem.

Deno already have a node compatibility mode, and will support import npm packages directly.

Re: Oven: The Company Behind Bun

#50
I have a lot of respect for Jarred and bun. The lean approach of just one person working for a year is rather underrated imo. No funding and therefore no pressure for growth. No overhead from scaling up a team and having to implement process, standards, etc. And at the same time, incredible content marketing by just tweeting about every little detail. Me and many others got hooked just because Jarred was posting interesting stuff and kept posting interesting stuff. It wasn't a stuffy blog or padded out conference talks, it was just good, technical content.

My only hope is that Jarred gets some rest for a bit. According to his Twitter he's been pulling 80 hour weeks and while that does lead to impressive work, it's not great from a human perspective. Hope he can rest up and keep this going for the long haul!

Post reply on HN