Journal Aug 22nd, 2022

  • Read Sustainable Web Manifesto - not really sure what to make of it. On one hand I totally get it, on the other who knows how to actually quantify this?
    • I know the Pixel 6 has a power rail that can be measured and you could look at the impact of loading a page in terms of power usage, but measuring on the client is only one aspect, how do you quantify the impact of any server interaction.
  • I was building a very simple site that made use of just plain old semantic HTML and no fancy styling or a need of a 'framework' for tables or columns, it's just a dynamic document and for the life of my my Google-fu failed me, so I asked a question on Twitter about needing a simple CSS frameworks - I'm very happy Twitter exists for questions like this. I couldn't think of the term that I wanted, but I had a vague notion of needing something that replaces the default stylesheet that the browser would apply (and I remember seeing one styled for Tufte). It turns out it's called no-class or Classless CSS< I'll keep that page up to date as I find more.
  • Deno gets me
    • I managed to finally get back to playing with Deno. It's good. Very very good.
    • For me, Deno Deploy is what Vercel once was. Quite happy so far with it. It just feels like building a web app.
    • I ended up writing my own request router and it was surprisingly smooth to get going. Code here if you are interested.
  • Read Color & Contrast
    • This is an incredible resource. I'm still reading it.

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, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.