I encourage folks to adopt this approach to keeping up with the JavaScript ecosystem: first do it, then do it right, then do it better.

Here’s my big secret for you today. When you design for the Web — that is, when you design exclusively and specifically for this medium — when you do that natively, so many of the things we consider problems just start to fall away.

The problem with polyfills is they prioritize developer convenience over user experience, while unnecessarily penalizing users on modern browsers by forcing them to download a lot of code they don’t need.

A half-jokingly short story that reveals some of the reasons why React may be as popular as it has become.

Hint: it’s all in the simplicity.

A tiny and simple side by side comparison of React & Angular 2.

A thing about javascript is that there seem to be a million differenct ways to package it up. The tooling is sometimes as impenetrable as the coding itself. I want to start by skipping all of that. I want to make the simplest simple app I can. How do I do this?

I wrote this article slowly over the course of the last four months. It’s the accumulation of examining many hundreds of JS and Node modules’ READMEs over the course of a few years, writing dozens of my own READMEs, digging into Perl’s history of documentation, and my personal thoughts.

Many web developers think the DOM is really difficult (or slow) and you need a huge framework to tame it. Then they invest a lot of their time to learn the framework. A year or two passes, another framework becomes popular and you need to learn everything from scratch. Repeat this a couple more times and JavaScript fatigue is born. Not to mention a huge pile of dependencies.