| ||Why does React.js truf other innovations like Cycle.js?|
6 points by stardrive on July 26, 2015 | hide | past | web | favorite | 9 comments |
|I'm surprised to read the following tweet, made yesterday by Sebastian Markbåge of the React team.|
"React tried and abandoned the Observable tree approach that @andrestaltz is using but but try out http://cycle.js.org/ incase we're wrong."
I agree Cycle.js is fully reactive while React.js is only partially reactive in it's state render function. Something that is missing in React.js is robust interaction and event handling. Both the front/data and back/event side of a app should be reactive and I think Cycle.js is just using Rx to show the way.
More React.js developers have seen the light of Rx recently so how can Rx be argued with? Maybe its just the MVI Framework that React.js does not like? Certainly Cycle.js brings a different sort of observable tree into the arena, exposing a whole new level of interactive computing for web apps.
Looking at another statement made by Sebastian Markbåge on April 10th, he admits that a better React.js event strategy is required. I see Cycle.js contributing to this acknowledged gap.
What is the verdict?
| Apply to YC