100
Some real benchmarks on Bun (compared with Node) -- It only wins sometimes, but it's mostly a fail (www.youtube.com)
submitted 2 years ago* by to c/programming@programming.dev
24 comments fedilink hide all child comments
 

Piped

Great watch but to summarize:

  • Bun beats Node/Yarn for package installation

  • Somewhat better API/DX in some ways.

  • Loses poorly in testing performance

  • Tons of incompatibility issues/performance issues in other areas.

General summary: Just don't use Bun yet, seems like it needs some more time in the oven.

you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 2 years ago (5 children)

I guess I don’t understand this obsession with speed? I work in development but I have never ran into a build that’s so slow that it impacts my work. Why is Node considered so bad that everyone wants to make is faster?

  • permalink
  • fedilink
  • source
  • hideshow 10 child comments
    •
  • [–] 12 points 2 years ago (1 child)

    You’ve never had an issue with how slow npm installs?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 2 years ago* (3 children)

    I'm with the parent poster. How often is it hindering your work?

    It's at tops, a 15-30 second wait, usually done at the start of the project.

    I'm a unique use ase, where I have about 10 projects (because microservices) that I'd have to npm install, and it's still not a pain to install them.

    Are people running npm install dozens of times a week on the same project? Because why?

    I'm not shitting on Bun. I'm actually supporting it's growth. But until it solves some real performance bottlenecks, (switching from gulp/webpack to vite changed our compiling time from 18 seconds to 2 seconds), I can't see any reason for people to change their workflow.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 2 years ago (1 child)

    It's at tops, a 15-30 second wait

    First: it can be a lot longer than 15-30s. One project I work on takes around 90s for a fresh install. This used to be worse in older versions of npm, and it's worse on Windows.

    Second: it also affects things like CI/CD. I prefer using Yarn 2+ for that reason (all dependencies are stored as part of your repo). It might not sound like much, but 30 extra seconds does decrease your productivity more than you might think if you have to wait for it every single time.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago

    Build times in nodejs are not so great in even medium size projects if you make heavy usage of advanced typescript features - either yourself or through libraries like zod. So if something makes the nodejs runtime faster, it could potentially make ts compiler faster too - for which I'd be very grateful.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago

    I guess I don’t understand this obsession with speed?

    for me it hasn't been build speed but rather execution

    I've run into problems with dayjs slowing down requests where I need to do a lot of processing. There are arguments to be made about replacing dayjs with datefns and how I should've been doing it differently anyway, but fact is that if the whole execution environment was twice as fast, it probably wouldn't have been much of a problem at all

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago

    because speed = your page loading fast = more clients = more satisfied clients = less environmental impact = less build time = less time downloading and lock-ing modules = more time for you ... the list goes on.

    I dont understand why is it so hard to understand that ... guys ... speed ... does ... matter? Our time matters? Our anything matters? And if you dont care, I do.

  • permalink
  • fedilink
  • source
  • parent