• wax@feddit.nu
    link
    fedilink
    English
    arrow-up
    5
    ·
    7 days ago

    It’s several distinct web views running simultaneously. I wonder why the memory footprint is not reused across these

  • crispbacon99@lemmy.zip
    link
    fedilink
    English
    arrow-up
    14
    ·
    7 days ago

    It’s the constant over use of DNS pings to track your location because its good data to sell

    • Ludicrous0251@piefed.zip
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 days ago

      Look fuck them but my PC location data has got to be the least juicy datapoint they could possibly ask for. Surprise, it stayed on my desk.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        7 days ago

        Javascript by itself isn’t an issue. Many applications use javascript without issue

        The problem is chromium and bloated graphical frameworks

        • pivot_root@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          7 days ago

          A few years ago, the Chromium blog had an article about how it improved energy use by dehydrating parts of the JavaScript standard library from a snapshot instead of initializing it on demand. From what I remember, the snapshot was hundreds of megabytes.

          ECMAScript, the core language is fine.

          JavaScript—with the DOM APIs—is not.