Comment on Some *real* benchmarks on Bun (compared with Node) -- It only wins *sometimes*

• Potatos_are_not_friends@lemmy.world ⁨1⁩ ⁨year⁩ ago

  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.

  Are people running npm install dozens of times a week? 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.

  source

  • FooBarrington@lemmy.world ⁨1⁩ ⁨year⁩ ago

    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.

    source

    • Miaou@jlai.lu ⁨1⁩ ⁨year⁩ ago

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

      source
  • snowe@programming.dev ⁨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.

    source
  • unique_hemp@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

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

    source