News for hackers. Stuff that matters.

A comment on Angular 2 versus React. Parent comment

Re:Angular 2 versus React by spankalee on Monday January 04, 2016 @05:26PM (#10839205)
You can manage state like that with web components as well: store state in one root object, only pass state down the tree, only build DOM based on the given state, use events to communicate changes back up the tree.

The end result is very React-like in behavior, but completely interoperable with other web components, and not require a framework at all.

[ Parent | on HN ]
Re:Angular 2 versus React by jbergens on Tuesday January 05, 2016 @07:21AM (#10842851)
This is what React does if you don't use Flux/Redux/something similar and it don't scale very well to medium sized or larger codebases.

Web Components hasn't been supported by all browsers (and probably still isn't) and has had some problems with grouping components and loading them. I can use React today but Web Components is something I might want to use in 2-3 years.

[ Parent | on HN ]