• sobchak@programming.devEnglish
      3·
      11 hours ago

      Is it just the HTML that should be under 14kb? I think script, CSS, and image (except embedded SVGs) are separate requests? So these should individually be under 14kb to get the benefit?

      • kibiz0r@midwest.socialEnglish
        3·
        8 hours ago

        Those additional requests will reuse the existing connection, so they’ll have more bandwidth at that point.

        • sobchak@programming.devEnglish
          2·
          8 hours ago

          Interesting, didn’t know that’s how modern browsers worked. Guess my understanding was outdated from the HTTP/1 standard.

      • xthexder@l.sw0.comEnglish
        4·
        10 hours ago

        In an ideal world, there’s enough CSS/JS inlined in the HTML that the page layout is consistent and usable without secondary requests.

      • hamFoilHat@lemmy.worldEnglish
        22·
        1 day ago

        I actually read the link and they mention QUIC

        there is a notion that HTTP/3 and QUIC will do away with the 14kB rule — this is not true. QUIC recommends the same 14kB rule.

        • mlg@lemmy.worldEnglish
          12·
          1 day ago

          Damn I was actually gonna add more context to my original comment about how QUIC is an overrated in place UDP upgrade for HTTP, but I didn’t wanna open my mouth because I haven’t read the QUIC spec.

          Thank you for this lol

          spoiler

          Sliding windows are for losers, spam packets at gigabit rates or go home /s