React Fire: Modernizing React DOM
Relevant: <a href="http:&#x2F;&#x2F;thecodist.com&#x2F;article&#x2F;the_programming_steamroller_waits_for_no_one" rel="nofollow">http:&#x2F;&#x2F;thecodist.com&#x2F;article&#x2F;the_programming_steamroller_wai...</a><p>“The Programming Steamroller Waits For No One“<p>Also:<p><a href="https:&#x2F;&#x2F;www.joelonsoftware.com&#x2F;2002&#x2F;01&#x2F;06&#x2F;fire-and-motion&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.joelonsoftware.com&#x2F;2002&#x2F;01&#x2F;06&#x2F;fire-and-motion&#x2F;</a><p>“Fire and Motion”<p><i>The companies who stumble are the ones who spend too much time reading tea leaves to figure out the future direction of Facebook. People get worried about React and decide to rewrite their whole architecture for React because they think they have to. Facebook is shooting at you, and it’s just cover fire so that they can move forward and you can’t, because this is how the game is played, Bubby. Are you going to support Saga? Flow? React Native? Are you supporting it because your customers need it, or because someone is firing at you and you feel like you have to respond?</i>