<story><title>React Fire: Modernizing React DOM</title><url>https://github.com/facebook/react/issues/13525</url></story><parent_chain></parent_chain><comment><author>coltonv</author><text>I love the react team for what they&amp;#x27;re doing here, but I have a feeling that the className -&amp;gt; class change would be a huge mistake. It makes it so that the ({ class }) =&amp;gt; ... syntax would no longer work since it&amp;#x27;s a reserved keyword. A simple find and replace is not going to work and a pretty sophisticated code mod would be required, and even then it still means convenient practical uses like the syntax mentioned above would never be possible.&lt;p&gt;It also brings up significant package compatibility issues, if even a single package I use uses className I can&amp;#x27;t upgrade React, if a single one uses class I can&amp;#x27;t upgrade it. I&amp;#x27;d rather not deal with a Python 2 -&amp;gt; 3 situation in React.</text></comment>
<story><title>React Fire: Modernizing React DOM</title><url>https://github.com/facebook/react/issues/13525</url></story><parent_chain></parent_chain><comment><author>icc97</author><text>I find it quite interesting how much of the public face of React that Dan Abramov has become. I really like the openness with which he speaks via his blog, but it feels like all the important React announcements come through him and I&amp;#x27;m sure there must be some other very senior FB developers who created React before he arrived who might not be so happy.</text></comment>