Programming

17669 readers

173 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

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 2 years ago

MODERATORS

snowe

Ategon

[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/programming

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

[–] [email protected] 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