News for hackers. Stuff that matters.
Re:React: Another Level of Indirection by Pacabel on Wednesday January 01, 2014 @09:51AM (#6995104)
I haven't used React, but the approach you describe sounds very much like how early C++ UI toolkits worked. Applications would be built of "reusable, nested components", often called "widgets". The widgets would be placed into a hierarchy, with widgets often creating their ancestors. Widgets would have a paint() method that would take the widget's internal state and the state of the widget's container(s) into account when displaying (or updating a previous display) of the widget.

- Pacabel

Re:React: Another Level of Indirection by pygy_ on Wednesday January 01, 2014 @11:13AM (#6995326)
Just to let you know: the guidelines ask not to sign your (otherwise perfectly good) comments.

http://ycombinator.com/newsguidelines.html

Re:React: Another Level of Indirection by wavefunction on Wednesday January 01, 2014 @12:43PM (#6995631)
One thing I'm not clear from your description is... The widgets were tightly-coupled with their ancestors? (In order to create them)
Re:React: Another Level of Indirection by ori_b on Wednesday January 01, 2014 @01:02PM (#6995715)
In general, no. You would typically take your widget, create it, and put it into a widget-agnostic container or layout manager. The widget wouldn't know about it's parent or children. The widgets would communicate by sending signals which bubbled up or down the container heirarchy, triggering repaints, resizes, and so on as needed.

Of course, this varied by toolkit.

Re:React: Another Level of Indirection by drcode on Thursday January 02, 2014 @11:37AM (#7000426)
You're only seeing one small similarity- React components are very different from old-school components.