They're trying to direct newbies away from mistakenly thinking ReactLink is the 'right way'. Seems to only exist so people coming from two way data binding cent

They're trying to direct newbies away from mistakenly thinking ReactLink is the 'right way'. Seems to only exist so people coming from two way data binding centric frameworks won't immediately discard React out of hand because it 'can't do two way data binding', before they get to know the framework's ideas and realise that two way data binding is usually a bad idea anyway; a notion which is fairly central to React's design. As an experienced React dev, I've never seen ReactLink in real-world use. See the docs page called Thinking in React [1] and grep through all the mentions of 'data flow' and you'll see how one way (circular) data flow is how React is intended to be used. [1] https://facebook.github.io/react/docs/thinking-in-react.html https://facebook.github.io/react/docs/thinking-in-react.html