<story><title>React v17.0 Release Candidate: No New Features</title><url>https://reactjs.org/blog/2020/08/10/react-v17-rc.html</url></story><parent_chain><item><author>simonw</author><text>&amp;quot;It has been two and a half years since the previous major release of React, which is a long time even by our standards!&amp;quot;&lt;p&gt;As a mostly Python and only occasional JavaScript developer, it always felt like the biggest challenge in the JavaScript community was how fast everything moved - new libraries, frameworks and ideas would tumble past at the rate of one every few weeks, and it felt impossible to keep up.&lt;p&gt;I&amp;#x27;ve been feeling that a lot less recently, and maybe the fact that React has been steady for 2.5 years is part of the reason.</text></item></parent_chain><comment><author>rhizome31</author><text>&amp;gt; As a mostly Python and only occasional JavaScript developer, it always felt like the biggest challenge in the JavaScript community was how fast everything moved&lt;p&gt;Those of us who were doing Python web dev in the years 2000s might remember that Python went through a similar period where it seemed that every week a new backend framework came out: Zope, CherryPy, web2py, Pylons, Django, repoze.bfg, TurboGears... to name a few. Nowadays it seems that everybody has settled for either Django or Flask. It might not have been as crazy as what happened with  JavaScript in the years 2010s but still I tend to see a similar pattern. People try a lot of different things, going in slightly different directions and eventually interesting approaches get identified and communities build up around a couple of solutions.&lt;p&gt;Meanwhile the Ruby community was able to build consensus around Ruby on Rails, with just Sinatra on the side for small projects.&lt;p&gt;I&amp;#x27;m wondering if this ability to try many different things might have been the cause for Python building numpy and eventually winning the scientific computing area as well.</text></comment>
<story><title>React v17.0 Release Candidate: No New Features</title><url>https://reactjs.org/blog/2020/08/10/react-v17-rc.html</url></story><parent_chain><item><author>simonw</author><text>&amp;quot;It has been two and a half years since the previous major release of React, which is a long time even by our standards!&amp;quot;&lt;p&gt;As a mostly Python and only occasional JavaScript developer, it always felt like the biggest challenge in the JavaScript community was how fast everything moved - new libraries, frameworks and ideas would tumble past at the rate of one every few weeks, and it felt impossible to keep up.&lt;p&gt;I&amp;#x27;ve been feeling that a lot less recently, and maybe the fact that React has been steady for 2.5 years is part of the reason.</text></item></parent_chain><comment><author>dawnerd</author><text>I second you on that. The number of times I&amp;#x27;ve had to rewrite code because a framework decided to break everything with little warning.. I don&amp;#x27;t even want to think about it actually. I get wanting to make code better but gesh people, do some planning and figure out a direction to move a project.&lt;p&gt;Also it seems JS devs don&amp;#x27;t understand semver either. Massive breaking changes in patch or minor versions are just evil.</text></comment>