Re:Don't React (Presentation - Use arrows to navigate)
by staltz on Wednesday December 31, 2014 @09:22AM
(#8819422)
Presentation author here. I should have taken this down before it popped up on HN or elsewhere. The video of this presentation is worth watching, because it's tongue-in-cheek through-out. But the slides are not worth reading, otherwise people take it seriously like it's happening here now. Cycle isn't the solution to everything, it's just one guy's ongoing experiment.
[ Parent
| on HN ]
Re:Don't React (Presentation - Use arrows to navigate)
by joelhooks on Wednesday December 31, 2014 @12:22PM
(#8820132)
The slides read great, and the concepts are important. It's something I'm personally intrigued by[1]. Very interested in Cycle and your experiments. Thanks!
[1] https://github.com/joelhooks/react-rxjs-angular-di-todomvc
Re:Don't React (Presentation - Use arrows to navigate)
by lhorie on Wednesday December 31, 2014 @09:26AM
(#8819437)
Do you have a link to the video?
Re:Don't React (Presentation - Use arrows to navigate)
by staltz on Wednesday December 31, 2014 @09:31AM
(#8819449)
Conference organizers will put it up and hopefully post it here: https://twitter.com/trewebdev
Re:Don't React (Presentation - Use arrows to navigate)
by jarkko on Wednesday January 07, 2015 @03:05AM
(#8849383)
Hot off the oven: https://www.youtube.com/watch?v=9QObt0SGriI&feature=youtu.be
Re:Don't React (Presentation - Use arrows to navigate)
by yogthos on Wednesday December 31, 2014 @10:29AM
(#8819694)
I find that Reagent http://reagent-project.github.io/ addresses many of the issues. For example, all components can be described as simple data structures. Components communicate via atoms that notify components that their state changes. This means that two components retain control over their state and can decide how they wish to react to the change in the atom.