“No one gets to tell us how to deal with the end of the world.”— Aeryn Michelle Williams, Luther Hargreeves, Tom Hopper, imdb.com
“People have to be angry at someone. But as leader, one cannot simply react to everything.”— Peter Morgan, Sir Winston Churchill, John Lithgow, imdb.com
“Things that are traditionally sync don’t have to “feel” sync. Things that are traditionally async don’t have to “feel” async. Be intentional and bridge the gap when you need.”— Dan Abramov, twitter.com
“Removing client-side React.js (but keeping it on the server) resulted in a 50% performance improvement on our landing page”— Netflix UI Engineers, twitter.com
“Interesting thing about React 16 SSR that is easy to miss. No more checksums means it can boot up from HTML that wasn’t generated by React.”— Dan Abramov, twitter.com
“The most important of which is the introduction of the pure render function that returns the representation of the UI based on the available data at that point in time.”— Zeit, zeit.co
“React tests have much less ceremony and are a bit easier to wrap your head around. And Test-Driven Development (TDD) with React captures the quick, fast iterations that make testing fun.”— Dave Ceddia, daveceddia.com
“We frequently ship new features and run hundreds of experiments every day, so we couldn’t freeze product development in order to rebuild our whole website in React. While it’s relatively easy to build a new web app in React, migrating a service that’s constantly changing and used by millions of peop…”— Imad Elyafi, engineering.pinterest.com
“Fiber is reimplementation of the stack, specialized for React components. You can think of a single fiber as a virtual stack frame.”— Andrew Clark, github.com
“When dealing with UIs, the problem is that if too much work is executed all at once, it can cause animations to drop frames and look choppy. What's more, some of that work may be unnecessary if it's superseded by a more recent update. This is where the comparison between UI components and function b…”— Andrew Clark, github.com
“The solution to caching GraphQL is to normalize the hierarchical response into a flat collection of records. Relay implements this cache as a map from IDs to records. Each record is a map from field names to field values. Records may also link to other records (allowing it to describe a cyclic graph…”— Facebook Engineering, facebook.github.io
“The snapshot artifact should be committed alongside code changes. We use pretty-format to make snapshots human-readable during code review. On subsequent test runs Jest will simply compare the rendered output with the previous snapshot. If they match, the test will pass. If they don't match, either…”— Christoph Pojer, facebook.github.io
“We use React.js and standard Flux for our application rendering and state handling, though a few teams have been experimenting with Redux as our future state container. We are also migrating our existing OOCSS/BEM-style CSS toolkit, called Superfine, into a set of CSS-encapsulated React.js UI compon…”— Lucie Lozinski, eng.uber.com
“If you’re writing React, you have access to a more powerful styling construct than CSS class names. You have components.”— michael chan, medium.com
“We value API stability because at Facebook we have more than 20 thousand components using React. This means that we are reluctant to change public APIs or behavior because teams depend on it both externally and internally.”— Facebook React Team, facebook.github.io
“Components written by different people should work well together. It is important to us that you can add functionality to a component without causing rippling changes throughout the codebase.”— Facebook React Team, facebook.github.io
“Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down.”— Josh Dover, gist.github.com
“Think of containers as structural components: they are fundamental for your code, but they don’t mean anything visually — they just define what data will be presented by the presentational components, and how they should behave.”— Alex Cordeiro, ckl.io
“Building a better developer experience has been one of the things that React deeply cares about, and a crucial part of it is to detect anti-patterns/potential errors early and provide helpful error messages when things (may) go wrong.”— Keyan Zhang, facebook.github.io