• Norgur@fedia.io
      link
      fedilink
      arrow-up
      10
      arrow-down
      8
      ·
      5 months ago

      That’s a really weird take. Like… what even is the difference supposed to be?

      This sounds more like “everything should be as it was back when <insert arbitrary point in time here>! When there were still Webpages, and we were frolicking about the internet! Until the fire nation attacked Web apps took over!”

      • Safipok@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        5 months ago

        Basically I am saying Firefox is not as performant as chromium when loading JavaScript.

        • TrickDacy@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          5 months ago

          Don’t agree, nothing noticeable for me anyhow. Chrome has the ultimate drawback: being under the control of a monopolistic evil corporation

        • Ananace@lemmy.ananace.dev
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          5 months ago

          In general, browser benchmarks seem to often favor Firefox in terms of startup and first interaction timings, and often favor Chrome when it comes to crunching large amounts of data through JavaScript.
          I.e. for pages which use small amounts of JavaScript, but call into it quickly after loading, Firefox tends to come out on top. But for pages which load lots of JavaScript and then run it constantly, Chrome tends to come out on top.

          We’re usually talking milliseconds-level of difference here though. So if you’re using a mobile browser or a low-power laptop, then the difference is often not measurable at all, unless the page is specifically optimized for one or the other.