This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan
<p>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.</p>
<p>This page is the list of ideas that I've had. There are likely many old drafts dating back many years.</p>
<p>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.</p>
<p>There are many errors in each of these articles, including and not limited to: spelling, grammatical, ecosystem awareness understanding and plain ignorance.</p>
<p>If you see something you like, don't like, then @ me (<a href="mailto:paulkinlan@google.com">paulkinlan@google.com</a>, @paul_kinlan) - I won't be offended.</p>
<p>Ideas (Note: this list will always be up to date):</p>
<ul>
<li><strong>Apr 4, 2021</strong> - <a href="https://paul.kinlan.me/are-developers-fixing-issues-identified-in-lighthouse/">Are developers fixing the issue identified by lighthouse</a> <br>
<blockquote>We don't know yet, but we can use HTTP Archive to find out</blockquote>
</li>
<li><strong>Apr 2, 2021</strong> - <a href="https://paul.kinlan.me/2020-web/">2020 Web</a> <br>
<blockquote>What can be safely used on the web in 2021.</blockquote>
</li>
<li><strong>Apr 2, 2021</strong> - <a href="https://paul.kinlan.me/chrome-dev-summit-2021/">Chrome Dev Summit 2021</a> <br>
<blockquote>What will Chrome Dev Summit 2022 looklike?</blockquote>
</li>
<li><strong>Apr 2, 2021</strong> - <a href="https://paul.kinlan.me/how-compatible-is-the-web/">How compatible is the web?</a> <br>
<blockquote>Is there a single number we can use to determine web compatibility?</blockquote>
</li>
<li><strong>Apr 2, 2021</strong> - <a href="https://paul.kinlan.me/ml-to-help-with-developer-experience/">Using ML to improve developer experience.</a> <br>
<blockquote>This is a massive WIP (there is nothing here yet). It's a place for me to store learnings.</blockquote>
</li>
<li><strong>Feb 2, 2021</strong> - <a href="https://paul.kinlan.me/instant-spa-without-js/">Instant SPA-without-js</a> <br>
<blockquote>akachan.app was built with no JS in the client, but is instant loading. JS in SW + Server.</blockquote>
</li>
<li><strong>Sep 23, 2020</strong> - <a href="https://paul.kinlan.me/mdn-browser-compatibility-report/">MDN Browser Compatibility Report</a> <br>
<blockquote>This was an HTML copy of the PDF version of MDN Annual Survey.</blockquote>
</li>
<li><strong>Jan 3, 2017</strong> - <a href="https://paul.kinlan.me/fullstack-wasm/">Fullstack Web Assembly</a> <br>
<blockquote>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.</blockquote>
</li>
<li><strong>Jun 2, 2016</strong> - <a href="https://paul.kinlan.me/shadowdom-and-progressive-enhancement-to-create-a-sharing-component/">Shadow DOM and Progressive Enhancement to create a Sharing component</a> <br>
<blockquote>I started to experiment with a way to build a sharing component that works everywhere.</blockquote>
</li>
<li><strong>Aug 7, 2015</strong> - <a href="https://paul.kinlan.me/the-reverse-polyfill/">Reverse Polyfilling</a> <br>
<blockquote>2015 thoughts on if we remove a feature from the web platform, should we provide a polyfill to help developers?</blockquote>
</li>
</ul>
This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan
