cyclejs

cebook/react/issues/3398 and https://twitter.com/sebmarkbage/status/543660526908088320 4. This presentation was given at a small meetup and I made it provocative on purpose just to have some fun with friends. The type of stuff you talk about in a small circle, not meant to publish on HN for the whole world https://www.youtube.com/watch?v=9QObt0SGriI 5. Cycle.js is not _better_ than React, it is my personal ongoing exploration in how to make React (or React's ideas) better. It is work in progress, and I'm breaking it apart whenever I find a better way of doing stuff. E.g. https://github.com/staltz/cycle/issues/99 6. Cycle.js is not an antagonist to React. I am currently experimenting with Cycle.js + React Native. https://github.com/staltz/cycle/issues/91 If React's API would be a bit less restrictive, I would use it for the web too. But virtual-dom by MattEsch is lighter and less restrictive, so I use that. 7. Don't be so harsh on HN as if I would be intentionally shouting to the whole world that React sucks.

do the same thing by updating an observable. For instance, you could have this.webSocketResponse = ko.observable() and call it with a new value for every websocket response you give. Now for me, the step beyond this is a library like Reactive Extensions (RxJS for Javascript) which instead of having stateful observables gives you async streams of events. For instance, say that you have two buttons, #1 and #2, and you want to do something when button one is pressed before button two: var buttonOne = $('#1'); var buttonOneClickStream = Rx.Observable.fromEvent(buttonOne, 'click'); var buttonTwo = $('#2'); var buttonTwoClickStream = Rx.Observable.fromEvent(buttonTwo, 'click'); var lastTwoClicks = buttonOneClickStream .map(function () { return 1; }) // clicking button one produces a 1 .merge( // merge buttonOneClickStream's output with the buttonTwoClickStream buttonTwoClickStream.map(function() { return 2; }) // clicking button two produces a 2 ) .bufferWithCount(2); // emit an array of two values once we have two values from our merged streams var firstThenSecond = function (arr) { return arr[0] === 1 && arr[1] === 2; }; var clickedFirstThenSecond = lastTwoClicks .filter(firstThenSecond); // only emit events that match our filter var notifyOnSuccess = clickedFirstThenSecond.subscribe(function() { console.log("woot"); }); The nice thing about this approach is that you can build up a variety of streams and merge them in a reusable and functional way. While this is possible in KO, I find that unless I'm very disciplined I ended up with a mess of computed properties scattered throughout my app. Since in KO we are using the observer pattern, which is stateful, this can cause some complexities. But with stateless streams, we have a more declaritive and perhaps even "imperative" approach. The step beyond this it to tie these streams into something more advanced than JQuery, like virtualdom. I started working on this only to find someone else has already accomplished a lot more than me in https://github.com/staltz/cycle However, I think I might like a template-based approach using something like handlebars. Anyways I'm quite tired so I might be mistaken in my assesment of this library. But I think anyone interested in reactive programming might like KO, RxJS, and Cycle. KO's worked quite nicely for me, despite my complaints about the limitations of stateful observers. Complete example of RxJS: http://jsfiddle.net/bjhyvvjs/ How to grok reactive programming: https://gist.github.com/staltz/868e7e9bc2a7b8c1f754 Why React.js isn't actually reactive: http://staltz.com/dont-react/#/ Edit: Argh I'm so sorry about the bad code rendering... I forgot to set translate_tabs_to_spaces in Sublime Text :( It should be good now!