We know that components and top-down data flow help us organize a large UI into small, independent, reusable pieces. However, we often can’t break complex components down any further because the logic is stateful and can’t be extracted to a function or another component. Sometimes that’s what people mean when they say React doesn’t let them “separate concerns.” |
|
A brief analysis and comparison of the CSS for Twitter’s PWA vs Twitter’s legacy desktop website. |
|
A complete real-world production example of a sophisticated webpack 4 config. |
|
Improving time-to-interactive (TTI) for Netflix.com on Desktop. |
|
“To make performance testing regular and routine, I try to distill the types of testing that we do into three distinct categories: Proactive, Reactive, and Passive. Each have their own time, place, purpose, focus, and audience.” |
|
Learn how to make your app faster by optimizing JS, CSS, images, fonts and other assets. |
|
In light of React hooks, Benedikt discusses approaches to optimizing the Array destructuring pattern relied upon by useState hooks. “In order to make it attractive to ship untranspiled code (to modern browsers), we’ll probably need to improve the way we deal with these special array destructuring (for multi-return values).” |
|
When to use, when to avoid, and how to set up your A/B testing stack. |
|
|
Comments