<story><title>Lessons from migrating a large codebase to React 16</title><url>https://blog.discordapp.com/lessons-from-migrating-a-large-codebase-to-react-16-e60e49102aa6</url></story><parent_chain></parent_chain><comment><author>gingerb</author><text>This is the reason why I still enjoy to write in C, there is simply no need to change your entire codebase because some dude came up with a new &amp;quot;miracle&amp;quot;.&lt;p&gt;I do full-stack javascript for my income, but have reached the point of not enjoying coding anymore because of this continuous change of ideas forced upon me. Why do I need to change from React.createClass to ES6 classes, from ESxx to Typescript or Flow, from React to Vue, from callbacks to Promises, from Flux to Redux, or from any idea to the next hyped idea?&lt;p&gt;When will people start to realise that this new method or technology they&amp;#x27;re implementing is deprecated already?&lt;p&gt;There is no end to this and I actually hate it as it destroys my passion for coding. I code to create things, not to continuously change what&amp;#x27;s created already and works fine.&lt;p&gt;As soon as I find a cool C job I&amp;#x27;ll definitely leave this mad house.</text></comment>
<story><title>Lessons from migrating a large codebase to React 16</title><url>https://blog.discordapp.com/lessons-from-migrating-a-large-codebase-to-react-16-e60e49102aa6</url></story><parent_chain></parent_chain><comment><author>chairmanwow</author><text>This seems like engineering for engineering&amp;#x27;s sake. From the author&amp;#x27;s description, this was a pretty superficial refactoring that may or may not have been for the better.&lt;p&gt;It seems like a bizarre decision to spend time migrating to a new system &amp;#x2F; tool that provides no immediate benefits. A thorough refactoring of their codebase seems like it would have been a better use of engineering time.</text></comment>