News for hackers. Stuff that matters.

A comment on First Impressions Using React Native. Parent comment

Re:First Impressions Using React Native by Touche on Friday February 06, 2015 @01:07PM (#9010468)
The other libraries intentionally left out shouldComponentUpdate because they don't think it's something a developer should have to worry about. I don't know of any evidence to suggest that React is faster because of this feature.

And declarative nesting is a feature of all of the frameworks I've come across, I'm not sure why you think that's unique to React. The advantage feature I would credit React for is the size of its community and influential advocates like you.

[ Parent | on HN ]
Re:First Impressions Using React Native by danabramov on Friday February 06, 2015 @01:43PM (#9010711)
>declarative nesting is a feature of all of the frameworks I've come across, I'm not sure why you think that's unique to React

Declarative nesting of lifecycle-ful and stateful components without going full FRP.

I'm actually excited to learn about other frameworks that do this! Which do you have in mind?

[ Parent | on HN ]
Re:First Impressions Using React Native by seanmcdirmid on Friday February 06, 2015 @09:55PM (#9012877)
WPF (even completely ignoring XAML), JavaFX both support declarative nesting with interesting databinding features to support it. They are based on retained scene graphs, however.

If you are interested in academics, I published such a system at ECOOP in 2006:

http://research.microsoft.com/pubs/179366/mcdirmid06superglu...

[ Parent | on HN ]