Love it or hate it, the JavaScript tooling landscape is the subject of a lot of chatter yet again.
The latest: Bun. A new JS runtime focused on performance and being all-in-one (runtime, bundler, package manager, transpiler). So think of it like Node.js, plus NPM, plus tsc, plus rollup - but faster.
It makes big claims, such as being 3x faster at server-side rendering React. So, we put it to the test.
What makes Bun fast?
The Bun team attributes their performance to a few things:
- Tons of time spent profiling, benchmarking and optimizing
- Using the Zig language for it's low-level memory control and lack of hidden control flow
- Using JavaScript Core, the engine inside of Safari, instead of V8, the engine inside of Chromium
So, is it faster?
We chose to dig into this specific claim from Bun.sh:
At first look, wow! But then I imagined my Next.js site suddenly being 3x faster... and just frankly found that hard to fathom.
But who knows, so I dug in. The first thing that stood out to me was the source code of the benchmark. To put it shortly... this is not the most "real life" example of a React app to server render.
I don't know about you, but every time I've server rendered React for a real app - theres a lot more going on. A much larger component tree with business logic, libraries, props, state, context, etc.
So I made a more full fledged React app, and decided to run some benchmarks.
Methodology
I created a dashboard app in Mitosis (source). It has a full tree of components, business logic, dependencies, uses props and state and other typical React features.
Mitosis was chosen so that we can generate code for many frameworks to compare their performance in this more "real world" oriented app, as well as variations - such as React vs Preact, CSS vs styled-components, etc.
I created a basic app with Node.js, Deno, and Bun. To more closely attempt to replicate Bun's results, note that we used their custom fork of react-dom/server.
I at first wanted to avoid this, but Jarred (the creator of Bun), made a good case for platform-specific implementations of react-dom/server is already a thing (such as browser vs node specifically), and likely will continue to be. They intend to merge this into React core ultimately, so we will cautiously optimistically assume this is on the horizon.
We then used autocannon to measure the throughput (requests per second) of each runtime server-rendering our React app.
So, what were the results?
Running on my 2.6 GHz 6-Core Intel Core i7, using Bun version 0.1.10, Deno version 1.25.0, Node.js version 16.14.0 my results were:
┌─────────┬──────────────────┬─────┬─────┬─────┬───────┬─────────┐
│ (index) │ name │ 1% │ 50% │ 99% │ Avg │ Std Dev │
├─────────┼──────────────────┼─────┼─────┼─────┼───────┼─────────┤
│ 0 │ 'react-ssr-bun' │ 500 │ 669 │ 718 │ 650.8 │ 71.7 │
│ 1 │ 'react-ssr-deno' │ 550 │ 600 │ 630 │ 601 │ 20.89 │
│ 2 │ 'react-ssr-node' │ 267 │ 375 │ 394 │ 366.5 │ 35.04 │
└─────────┴──────────────────┴─────┴─────┴─────┴───────┴─────────┘
View the full source for the benchmarks (and let me know if you see ways the methodology can improve).
In this, we are seeing Bun handling about 75% more requests per second than Node.js, with Deno falling in between (closer to Bun than Node).
I have to say, I was surprised. Yes, it's not 3x faster - but it is in fact faster by a healthy margin.
So, should I switch to Bun now?
Well, probably not. It is currently in beta and not production ready (with many users reporting that there are notable bugs). But it is likely worth keeping your eyes on.
I have to say, using the Bun CLI in particular feels very snappy.
Installation in particular feels so fast I have to double take to confirm to myself that it actually happened.
To me, this is one of the more exciting areas of Bun, considering how slow even Yarn can be in my experience for medium to large projects.
But, this is just one person's results and opinion. What do you all think?
Top comments (37)
Not ideal for whom? Some of us like that kind of work environment. You act as though there is some ethical code is being violated. Is there a new ethic against hard word and long hours now? I missed that memo.
No one forces you to sign an agreement, lol. The conditions are transparent and known beforehand.
According to your logic, it’s not ok for banks to issue loans since they just steal your money. You took from them 100 USD, but you owe them 110 USD. That’s definitely a deceive, I think we should sue them. F*ck the agreement, we will just tell them the logic of Luke Shiru.
It is an awesome tweet for a company which have all chances to influence the future. Same to "There are way easier places to work, but nobody ever changed the world on 40 hours a week""
Well, Brendan Eich changed the world in 10 days with JavaScript.
Agree, but in which direction 😅
Work ethic(s), there’s irony here. It’s not a company, it’s a startup, I’m sure equity is part of the package.
I don't understand. If overtime hours are paid and you signed an agreement which is clearly saying that sometimes you would stay overtime and get paid for that. Where is the problem?
Thanks for sharing Steve, I will definitely keep an eye on Bun!
Calm down, the friend there didn't say that there is no exploitation nor did he make any absurd point. Exploitation certainly exists in large corporations, but that doesn't mean overtime is exploitative, you're just looking at things from the employee's side when the dance is two-way, the programmer is not obligated to work at that company if he doesn't want to. in no way do overtime, and that is specifically why it is not exploitation, or at least, it is not unwarranted or negative exploitation per se. Things would be different if we were talking about people like Beezos for example, they are cases and cases that need to be analyzed. It also doesn't mean he thinks these extra hours are cool or that he's not being "empathetic to other devs", just that he's considering all facets of this issue.
Okay, I would choose my friend. What about 100k loan for opening up my new business? Would a friend give me this amount of money? If yes (because I don't know about your friends, mine are not that rich), then are you 100% sure, that your friend would not expect a share in your business or at least some percent off 100k, say 2-3%? Money is not free, your friend could choose a deposit in the bank or buy Tesla shares or else.
Let me point this out: no one in the comment section or in the actual post tried to shill Oven job to you or anyone else. Let's just admit: YOU started the thread about their work culture, and now you are complaining that someone might have recommended this job to you.
If you don't recommend the job, it's totally fine. That's your opinion. But there are other people with their opinions who think it's totally fine to work there. Again: it's totally legal, so no one should worry about. Just DYOR about the company and make your own choice. It's like you are trying to ban this company just because you don't like it. Well, if you don't like it, don't work there. It's that simple, yes
If I had a company and I needed my employees to work more than the established hours, I would ask them, and if it was within my power, I would reward them properly for their effort. Of course what I would do is not what you would do, or what this company did, I am not approving or disapproving of their behavior but simply pointing out that this is not an exploratory act per se and that it may actually be justifiable depending on of the circumstances.
Mandatory overtime isn’t exploitation. Nobody is being forced to work there, and it’s not slave labor. Some devs want the extra money from working overtime.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.