Journal Jun 23rd, 2022

  • Read
    • Don't disagree.
  • Read Kino
    • Great web site built by a part of the Chrome team that explains media a little more and has some interactive demos integrated in.
  • Read Style scoping versus shadow DOM: which is fastest? | Read the Tea Leaves
    • I'm very glad they have pricing, but I'm looking at it and I'm like, damn, I can't even experiment.
      • The ideas that I can come up with are all fun interactive kind of things and I'd hate to get on the end of a HN stampeded.
      • "browser profile identifier" - wonder how that works (or will work) as all of the browsers try to move to a world with less profiling.
    • Your app is built as a replicache app - it's not like you just hook it in and it takes your local state and syncs it, you have to build it knowing that you will structure your app that way. It's not a bad thing per-se, but you are locked in to it.
    • - Good quick start!
    • Demos are very good too.
      • Moreover, an important characteristic of CRDTs is that they support decentralised operation: they do not assume the use of a single server, so they can be used in peer-to-peer networks and other decentralised settings. In this regard CRDTs differ from the algorithms used by Google Docs, Trello, and Figma, which require all communication between users to flow via a server.

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.