News for hackers. Stuff that matters.
Re:Lessons from migrating a large codebase to React 16 by Touche on Tuesday November 07, 2017 @09:13AM (#15643464)
> All of these old things still work.

The old things likely have bugs. And most libraries don't spend a lot of time patching old versions (why should they, it's free software). The longer time passes the less and less likely there will be bug/security patches. So if you want to own those bugs/security issues, sure, stay behind to avoid the cost of upgrading.

Re:Lessons from migrating a large codebase to React 16 by mattferderer on Tuesday November 07, 2017 @10:48AM (#15644351)
There are "enterprise type" libraries for JavaScript developers that move slower & focus on stability over performance or productivity increases. Some are backed by a company that offers paid support. While I haven't used it, I've heard good things about Telerik.
Re:Lessons from migrating a large codebase to React 16 by jjawssd on Tuesday November 07, 2017 @12:03PM (#15645115)
Where can we learn more about these "enterprise type" libraries?
Re:Lessons from migrating a large codebase to React 16 by zackify on Tuesday November 07, 2017 @10:44AM (#15644300)
"The old things likely have bugs" Do you even have experience with React? It sounds like you don't. Because there's no "bugs" with using createClass or proptypes, it's simply been split out into a separate package that you can still use if you want.
Re:Lessons from migrating a large codebase to React 16 by zackify on Thursday November 09, 2017 @01:13PM (#15664502)
Lol love how I get downvotes for stating facts