Earlier quoted context omitted.
Deno already have a node compatibility mode, and will support import npm packages directly.
Sure, but it doesn't because initially they chose not to.
it was a very wise choice.
Oven: The Company Behind Bun
91–100 of 122 posts
Re: Oven: The Company Behind Bun
#92Earlier 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?
There's no secret sauce Just lots of time spent profiling and trying things On the runtime side, JavaScriptCore/WebKit's team are extremely receptive to feedback, especially performance-related. Today, @Constellation made `Promise.all` about 30% faster https://github.com/WebKit/WebKit/pull/3569
Have you done any comparisons with Graal’s NodeJS runtime?
Re: Oven: The Company Behind Bun
#93Re: Oven: The Company Behind Bun
#94Earlier quoted context omitted.
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.
It's not actually nonsense, some minor edits will make it clear.
> Why do they call it oven when you "oven" (of in) the cold food and "oveout" (of out) the hot food to eat?
Re: Oven: The Company Behind Bun
#95Interesting effort. How do you plan to make money? I would love to do something like this but it must be really hard to figure how to turn revenue sustainably apart from donations, consulting and maybe some sort of hosting services.
Re: Oven: The Company Behind Bun
#96For those like me who didn't know:
https://bun.sh/. "Bun is a fast all-in-one JavaScript runtime. Bundle, transpile, install and run JavaScript & TypeScript projects — all in Bun. Bun is a new JavaScript runtime with a native bundler, transpiler, task runner and npm client built-in."
Re: Oven: The Company Behind Bun
#97Earlier quoted context omitted.
There is definitely a gradient in safety and almost everybody agree with that. What is controversial is how much safety you actually need.
I misspoke, there is a gradient in safety, but "memory safe" is binary.
There is in fact a spectrum with respect to memory safety. For example, temporal vs spatial safety.
Furthermore, no language is “memory safe” in the absolute sense. For example, not even the borrow checker can protect you from buffer bleeds.
Re: Oven: The Company Behind Bun
#98It'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…
> though I worry about the use of an unproven language
Maybe this will be the company that proves it :)
Re: Oven: The Company Behind Bun
#99Earlier quoted context omitted.
Is there not a gradient though? Are C++ smart pointers equally as bad as regular old malloc? Can safer abstractions not render most buffer overflows impossible?
I misspoke. Yes, security is on a gradient and the things I've listed have caught and prevented many, many bugs, but memory safety is a binary proposition. Those things have not made C++ "memory safe".
[deleted]
Re: Oven: The Company Behind Bun
#100For those like me who didn't know: https://bun.sh/ . "Bun is a fast all-in-one JavaScript runtime. Bundle, transpile, install and run JavaScript & TypeScript projects — all in Bun. Bun is a new JavaScript runtime with a native bundler, transpiler, task runner and npm client built-in."
"Run TypeScript" is misnomer, unless I'm missing something, it compiles TS -> JS and "runs" that.