News for hackers. Stuff that matters.
Re:React Concurrent Mode by huy-nguyen on Thursday October 24, 2019 @03:34PM (#21348375)
The important thing to remember here is that you don't have to use all of these newfangled features. As stated in the write up, these are primitives for library developers (e.g. apollo-graphql) to build on top of. The only real development that affects end-users in the past year or so is the migration to function components but even then, you can keep using class components (although you do have to rename some method names but even then, the React team provides automatic codemods for that).
Re:React Concurrent Mode by com2kid on Friday October 25, 2019 @03:16AM (#21352656)
> The only real development that affects end-users in the past year or so is the migration to function components

Except for those of us using React Native, where functional components break live editing!

Thankfully a fix for that is coming soon, in a other 2 or 3 months maybe I can start using hooks... :/

Re:React Concurrent Mode by vast on Friday October 25, 2019 @02:39AM (#21352497)
"You don't have to use it" is a very common statement when a part of the userbase battles feature creep, complexity or just bad decisions. And it is always a lie. Most projects are driven by collectives or passed to new maintainers, which naturally takes this choice away from you. Optional is never optional.