Raja gives us a great compilation of everything that joined the ranks of JavaScript in recent years.

Kat proposes an as keyword for destructuring patterns, so that you could write code like the following.

function maybe({ debug } as options) {
  if (debug) {
    console.log({ options })
  }
}

An interesting proposal, and something that I also feel that is missing from destructuring.

“With NEL, you can instruct user agents to collect the same set of information that would appear in your server logs. Those instructions would apply to all requests to your server’s origin, regardless of how (and on which containing sites) those requests were initiated. And since the data is collected directly by the user agent, you should have visibility into all of your clients’ connection requests, not just those that made it to your serving infrastructure.”

JavaScript Proxies are a powerful feature that can be used for solving various problems elegantly. Arfat examines Sindre Sorhus’ new on-change library to explain how proxies work.

Allison provides strategies that build performance culture from the long term, from starting a performance culture at your company to educating and empowering teams to understand and own their products’ performance.

Ben shares improvements and measurements that can be put in place to optimize load times in a complex web application.

An attempt to provide a correct, yet modern, introduction to the DNS set of RFC specifications.

A simple replacement for enzyme that encourages good testing practices.