I've been thinking about a lot about the state of modern web development and I wanted a place to note ideas, and then over time build up them in a way that is a little more open that me just dumping them into a Google Doc and forgetting about them.
This page is the list of ideas that I've had. There are likely many old drafts dating back many years.
These documents are completely un-developed and are a snapshot of my thoughts at the time. They will be refined over time with research, education and conversations with people in the industry, and in some cases I might delete it.
There are many errors in each of these articles, including and not limited to: spelling, grammatical, ecosystem awareness understanding and plain ignorance.
If you see something you like, don't like, then @ me (email@example.com, @paul_kinlan) - I won't be offended.
Ideas (Note: this list will always be up to date):
- Apr 4, 2021 - Are developers fixing the issue identified by lighthouse
We don't know yet, but we can use HTTP Archive to find out
- Apr 2, 2021 - 2020 Web
What can be safely used on the web in 2021.
- Apr 2, 2021 - Chrome Dev Summit 2021
What will Chrome Dev Summit 2022 looklike?
- Apr 2, 2021 - How compatible is the web?
Is there a single number we can use to determine web compatibility?
- Apr 2, 2021 - Using ML to improve developer experience.
This is a massive WIP (there is nothing here yet). It's a place for me to store learnings.
- Feb 2, 2021 - Instant SPA-without-js
akachan.app was built with no JS in the client, but is instant loading. JS in SW + Server.
- Sep 23, 2020 - MDN Browser Compatibility Report
This was an HTML copy of the PDF version of MDN Annual Survey.
- Jan 3, 2017 - Fullstack Web Assembly
I've been thinking about how code compiled with WASM could be shipped in the browser, shipped via the client, and also run on the server.
- Jun 2, 2016 - Shadow DOM and Progressive Enhancement to create a Sharing component
I started to experiment with a way to build a sharing component that works everywhere.
- Aug 7, 2015 - Reverse Polyfilling
2015 thoughts on if we remove a feature from the web platform, should we provide a polyfill to help developers?
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.