News for hackers. Stuff that matters.
Re:Reactive.coffee: reactive programming and declarative UIs... by invalidOrTaken on Wednesday August 07, 2013 @02:36PM (#6174698)
Do you feel that you've lost anything in terms of composeability as compared to a more stream/combinator-oriented approach, like, say, Flapjax? If so, have you found that painful in the real world, or do you think it's more of an academic concern with little meaningful impact?
Re:Reactive.coffee: reactive programming and declarative UIs... by xyzzyrz on Wednesday August 07, 2013 @03:25PM (#6175029)
Good question - the reason why we built the library this way was exactly because we find declaring expressions to be more natural than wiring together streams by combinators—which, BTW, Flapjax does support. Far from academic-without-impact, Leo's work was actually directly influential on me—esp. since he worked in PL and I didn't, so much of my initial exposure to reactive programming came from a few projects including his.
Re:Reactive.coffee: reactive programming and declarative UIs... by alipang on Wednesday August 07, 2013 @04:20PM (#6175344)
I'm a big fan of bacon.js. Is there any way you can abstract over values over time, or asynchronously? This was always my big problem with knockout.