Web Excursions 2021-11-19

Twitter Rolls Back AMP Support, No Longer Sends Users to AMP Pages | Hacker News


From a technical perspective, AMP had two, intertwined goals:

  1. allow third parties to safely rehost your page,

    • so that they could provide a seamless preloading experience—fetch & render the page in the background,

      • and display it to the user immediately when they click a link.

    • This massively improved the time it took to load search results on mobile web,

      • since it moves the request out of the critical path and allows Google's CDN to serve your assets.

  2. Provide a front end framework that focused on performance and UX,

    • forcing developers to get rid of layout shifts, weird scroll effects, and other things that made mobile web browsing a nightmare.

    • This framework allowed for a limited subset of HTML and CSS, but no custom JS, allowing it to enforce these rules for all rehosted pages.


  • Non-technical users that don't care about the shady things Google did involving AMP probably think AMP is a godsend, if they even know AMP is even a thing.

  • AMP pages load incredibly fast, are incredibly responsive, and are far less annoying.

    • Your typical end user will likely prefer AMP.

  • Thing is...we don't need AMP to get those features.

  • But somewhere along the last 10 years, web developers lost the plot and now seem to think a static blog needs to serve several megabytes of JavaScript.

  • They think they need to implement smooth scrolling in code, when every browser already does it natively.

About a third of news organizations have already adopted a remote or hybrid working model » Nieman Journalism Lab

  • Publishers are reporting some unexpected benefits from hybrid working.

  • Reuters reported higher attendance and more “meritocratic” discussions when meetings were held on Microsoft Teams

    • rather than behind glass walls in the physical newsroom.

  • “When participants are all the same squares on a digital video platform, those old hierarchies — who sits at the top of the table or next to whom — are suddenly less visible and less imposing”

Japanese Tongue Twisters | Nippon.com

  • A maiden win for Sumomomomomomomomo at a Tokyo racecourse on November 1, 2021,

    • put the spotlight on an up-and-coming three-year-old filly with a repetitious moniker.

  • The horse takes her name from the Japanese tongue twister:

    • Sumomo mo momo mo momo no uchi (スモモも、モモも、モモのうち),

    • meaning “Both sumomo and peaches are kinds of peaches.”

  • A sumomo is a kind of plum (Prunus salicina), sometimes called the “Japanese plum,”

    • although not to be confused with the famous ume.

    • Botanically, it cannot really said to be a kind of peach (momo),

      • which is only a close relation (Prunus persica).

    • Still, the linguistic connection might be enough;

    • at the word level, at least, we could say a sumomo is a kind of momo.