Most breaking changes are including warnings 2 versions ahead of time... In TFA they outlined, iirc, 2 changes that would have less time than this.  This isn&#x27;t a magical, final interface we&#x27;re dealing with... it&#x27;s iterative changes over time.<p>TBH, I don&#x27;t like getting stuck at one point.. in practice those using React have been embracing the one-way flow that flux-like frameworks bring... This has been distilled down to Redux (imo, the best workflow option for React), which has signalled some distillation in terms of the interfaces React exposes.  This is combined with different rendering paths coming to light, and I think it&#x27;s pretty great.<p>I&#x27;m currently working in an environment that is transitioning from the old-way, to a more current way of doing things.  I&#x27;ve been working with node since pretty early on (0.4) and was following it before that.  The more I&#x27;ve embraced this continuously updating workflow, the less friction I&#x27;ve experienced as a whole.  That doesn&#x27;t mean no pain, just less of it overall.<p>The React&#x2F;Facebook guys have been very good members in this larger community, and I applaud them for their efforts...  Dropping their own render in favor of Babel, and reducing some of their mutation enablers only show them to be working with feedback from the community.  It may be at a pace that&#x27;s harder to keep up with, but that doesn&#x27;t mean that they shouldn&#x27;t be doing it.