Introduction to React.js
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about how React's virtual DOM, rendering model and lack of explicit data binding work, citing the creators directly.
Recommended by 1 people across 1 different months, 2019 to 2021.
What it is
A 2013 talk from Facebook Seattle in which Tom Occhino and Jordan Walke, two of React's creators, introduce React.js. They cover the rendering model, the virtual DOM idea and how React differs from data-binding frameworks.
What people said
Recommends Jason Y · 2019-12 · Stack Overflow · on “How React Virtual Dom is faster? At the end of all its going to hit call browser API to update the real DOM”
Here is a talk given circa 2013 (v0.4.0) by the two guys behind React. They describe exactly how it works. Unlike data binding and dirty checking (Angular, etc.) React uses one render method that's called recursively. It then generates a long string that is a representation of the DOM. The concept is actually really simple. [this video]
Cites Subrato Pattanaik · 2020-09 · Stack Overflow · on “No explicit Data binding in React JS”
Tom Occhino said in his presentation that there is "No Explicit Data Binding" especially in React.js. Check out the presentation video here [this video] and go to 7:30 minute where he said that before. Why there is "No explicit data binding" in React JS?
Cites Subrato Pattanaik · 2020-09 · Stack Overflow · on “No explicit Data binding in React JS”
Now I have understood with explicit data binding in JS. But Tom Occhino said in the presentation that "No explicit data binding" in react. Check the presentation video here [this video] . (7:30 exact)
Cites Janez Kuhar · 2021-02 · Stack Overflow · on “Recursive component rendering based on a tree menu object”
From @LindaPaiste's answer: When changing a value that is not the last in the path, you need to clear all subsequent selections because they were based on a different path. That's the key to solving your problem! You have to somehow blow away and forget everything bellow the selection box whose value you are currently changing. React was designed around the "blow away and forget" principle [this video] . Note also that The Data Flows Down [LINK] . With that in mind, your task should be fairly easy to complete and while Linda's solution seems to work, it is perhaps not as simple as it could be. What if we could have a special component that (1) accepts a sub-tree of your data, (2) renders its 1st