Developer Clarity

  • Drip feed of API's
  • Deprecate and Break. Recent events were a stark reminder that empathy is key.
  • Time for a change.
    • On one hand people don't like Apple's model of ship twice a year with an OS update, on the other Chrome is pushing too quickly. Alex Komoroske talked about elastic band and tension and stretch too far it snaps.
      • Have we reached that points
    • web.dev - appears Chrome only.
      • too much change.
      • too quickly.
    • Refernce - too fast, can't keep up. Other's shouldn't have to work because of our lack of support.
    • How can we slow down, but keep pace? Maybe batch more. The general population of developers don't need to know about all new API's on the day they launch.

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.