- The Bullshit Web — Pixel Envy
- Read The Web is not Poor Man’s Native | in progress
- Comments: The web is not poor man’s native (2015) | Hacker News - It was interesting to read
- Reflecting on how I write these notes - I read a lot of websites and then I drop the link in to
logseqand then use my plugin to get the pages title, I noticed everyone always has the site name at the end of the page "— {title}" or "| {title}" and I'm just left wondering why there isn't a<site>element (or something similar) that you can use to describe the site or origin that the page is on. It's visually unappealing for me, but more broadly I wonder how it's rendered in other assistive technology?- There is
<meta name="application-name">that does something kinda similar. - schema.org has https://schema.org/WebSite and an associated name.
- Am I missing something?
- There is
- WHATWG Stream Visualizer by Surma (use's titles right ;))
- Was very happy to stumble across this. I was thinking about this more in the context of WebCodecs and being able to visually construct the TransformStream to generate frames.
- Read sharp - High performance Node.js image processing
- Read Five things we've learned about Web Stories
- I just don't see them - I find it interesting that Google still does roll outs just in specific locales, but the messaging is global :\
About Me: Paul Kinlan
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.
