News for hackers. Stuff that matters.

A comment on React Concurrent Mode. Parent comment

Re:React Concurrent Mode by couchand on Thursday October 24, 2019 @02:53PM (#21347923)
No, React was created in opposition to the fact that we used to manually update the DOM because that's all we had tools for.
[ Parent | on HN ]
Re:React Concurrent Mode by PKop on Thursday October 24, 2019 @03:05PM (#21348062)
Rethinking best practices absolutely addressed misapplication of separation of concerns.

https://www.youtube.com/watch?v=x7cQ3mrcKaY

Components have always had JSX markup along with data manipulation logic. CSS in JS and styling co-located with component extended this consolidation of cross-cutting concerns.

These, along with not manually updating DOM state as you mention, all fall under declarative aspects of React.. which concurrent rendering and Suspense are consistent with and essentially an extension of.

[ Parent | on HN ]
Re:React Concurrent Mode by mosdl on Thursday October 24, 2019 @08:50PM (#21350732)
No, React was created to allow contractors to write code fast and not worry about optimization.
[ Parent | on HN ]