this post was submitted on 17 Sep 2023
100 points (96.3% liked)

Programming

17299 readers
682 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
100
Some real benchmarks on Bun (compared with Node) -- It only wins sometimes, but it's mostly a fail (www.youtube.com)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
22 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
[–] Potatos_are_not_friends 8 points 1 year ago* (last edited 1 year 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.

[–] FooBarrington 5 points 1 year ago (1 children)

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.

[–] [email protected] 6 points 1 year ago

Ugh as a system developer I'm happy when compiling anything takes less than 5min

[–] [email protected] 3 points 1 year ago

Hmm, npm can take up to five minutes for me. I usually just leave it alone and go do other stuff. And I have fiber internet, so it’s not download speed that’s the problem.

[–] [email protected] 1 points 1 year ago

Webpack takes 10 minutes to build the release bundle in a project at work...