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

WalkableProgrammer@lemmy.world ⁨1⁩ ⁨year⁩ ago

• snowe@programming.dev ⁨1⁩ ⁨year⁩ ago

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

  source

  • 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
• lorefnon@programming.dev ⁨1⁩ ⁨year⁩ 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.

  source
• fiah@discuss.tchncs.de ⁨1⁩ ⁨year⁩ 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

  source
• Virkkunen@kbin.social ⁨1⁩ ⁨year⁩ ago

  I don't understand it either.

  I've only had issues with npm speeds when the projects were stored in a HDD, and that's not node's fault.

  source
• exapsy@programming.dev ⁨1⁩ ⁨year⁩ 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.

  source