• milliams@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    18 hours ago

    I was going to be rude, but I thought I’d just do you the courtesy and paste the relevant section from the article:

    As it tends to be heavily trafficked, the overall bandwidth is a key consideration, and to that end one of the changes we made this week was to split the page content into a more basic page, augmented by a separate Javascript file with additional content beyond that. Since most of the traffic to the site is automated it tends not to fetch the Javascript file, reducing overall data requirements.

    They’re using JS to reduce the load.

    • urushitan 漆たん@kakera.kintsugi.moe
      link
      fedilink
      English
      arrow-up
      2
      ·
      18 hours ago

      Yeah specifically the JS holds translated versions of the sentence “This domain is for use in documentation examples without needing permission. This is not a service; avoid relying on it for testing and monitoring purposes.” The raw HTML returns just that + CSS. The JS injects translations of that sentence in multiple languages

        • psion1369@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 hours ago

          So basically what is happening now. The JS allows it to happen on the client side, taking a HUGE load off the server trying to parse the ua string, find the right translation, bring up the file, and respond. They probably have a single binary that has the HTML, CSS, and JS all compiled in and update it once every year.