4 ms·

Hey there! I'm on the FB/IG React core team. Syntax differences aside, seems to me that React is geared more towards interactive UI components and Ractive is o

Hey there! I'm on the FB/IG React core team. Syntax differences aside, seems to me that React is geared more towards interactive UI components and Ractive is oriented more towards reactive documents, kind of like Tangle[1]. Is this accurate? The similarity seems to be in the philosophy of the implementation (manipulating a fast representation and rendering to the DOM). It's pretty cool to see that we both discovered the "secret" though :) Seems like we're validating each others' projects! If you ever want to nerd out we hang out in #reactjs on freenode. [1] http://worrydream.com/Tangle/ http://worrydream.com/Tangle/

rich_harris 13y ago
Hi! Yes, I was excited when React came out because it demonstrated that I wasn't the only one who felt that these problems hadn't been fully solved yet (though a part of me thought 'well I may as well give up now...'), Yes, you could draw the Tangle comparison, though I think there's probably a fair amount of overlap - a couple of the Ractive examples are recreations of React/Angular demonstrations. Looking forward to spending some more time with the React source code to try and learn your secrets!
mateusmaso 13y ago
I agree with React being geared more towards interactive UI components, but on the other hand you could use Ractive with WebComponents/Polymer instead of MDV to get all this powerful component lifecycle. Still working on a solution that mix Backbone for core models + Polymer for view lifecycle and custom elements + Ractive for awesomeness updating. The only concern I have is that some people do not like to use logicless.. I think React is powerful for letting you declare full javascript evaluations and expressions on your template code and giving you more flexible/productive way of writing.
- rich_harris 13y ago
  Ractive does have a way of including JavaScript evaluations in the template which as far as I'm aware is unique: http://learn.ractivejs.org/#!/expressions/1 http://learn.ractivejs.org/#!/expressions/1 The JavaScript expression is parsed into an AST, and references to parts of the data model are extracted so they can be dependency tracked and evaluated against the right context. Quite hard to explain concisely but I think it does what you're after.

rich_harris 13y ago

Hi! Yes, I was excited when React came out because it demonstrated that I wasn't the only one who felt that these problems hadn't been fully solved yet (though a part of me thought 'well I may as well give up now...'), Yes, you could draw the Tangle comparison, though I think there's probably a fair amount of overlap - a couple of the Ractive examples are recreations of React/Angular demonstrations. Looking forward to spending some more time with the React source code to try and learn your secrets!

mateusmaso 13y ago

I agree with React being geared more towards interactive UI components, but on the other hand you could use Ractive with WebComponents/Polymer instead of MDV to get all this powerful component lifecycle. Still working on a solution that mix Backbone for core models + Polymer for view lifecycle and custom elements + Ractive for awesomeness updating. The only concern I have is that some people do not like to use logicless.. I think React is powerful for letting you declare full javascript evaluations and expressions on your template code and giving you more flexible/productive way of writing.

rich_harris 13y ago
Ractive does have a way of including JavaScript evaluations in the template which as far as I'm aware is unique: http://learn.ractivejs.org/#!/expressions/1 http://learn.ractivejs.org/#!/expressions/1 The JavaScript expression is parsed into an AST, and references to parts of the data model are extracted so they can be dependency tracked and evaluated against the right context. Quite hard to explain concisely but I think it does what you're after.