GitHub - staltz/cycle-onionify: MIGRATED! This was transfered to https://cycle.js.org/api/state.html
André Staltz - Why we built xstream
For the past two years I have been using RxJS extensively, in Cycle.js and in other contexts. Recently, TylorS and I have decided to build a new reactive streams library comparable to RxJS, called xstream. TL;DR: we needed a reactive stream library tailored for Cycle.js. It needs to be “hot” only, so users don’t need to think about subscription semantics hidden in drivers. It should have only a fe
André Staltz - The reducer pattern in Cycle.js
The “reducer” pattern from Redux (or the “update” pattern from the Elm architecture) is common also in Cycle.js, except there is no switch-case (or pattern matching block) because each reducer corresponds to one (and only one) action. See this example code where each action stream is being mapped to a “reducer” function. const setHighlightReducer$ = actions.setHighlight$ .map(highlighted => functi
MVI (Model-View-Intent) と MVC との違い - Qiita
Cycle.js の MODEL-VIEW-INTENT のチュートリアルから MVI (Model-View-Intent) と MVC (Model-View-Controller) に関する説明を抜粋して翻訳しました。原文のライセンスは MIT です。 「Passive/Reactive プログラミングの違いを学ぶ」 をあらかじめ読んでおくと理解が深まるでしょう。筆者の André Staltz さんは Flux、Redux などのアーキテクチャの比較や評価を UNIDIRECTIONAL USER INTERFACE ARCHITECTURES と NOTHING NEW IN REACT AND FLUX EXCEPT ONE THING の記事で述べています。 MVI (Model-View-Intent) について MVI は Cycle.js の main() 関数を3つの
Cycle.js and functional reactive user interfaces
Presented at Reactive 2015. React's future is going to be more functional, and less OOP. What if that future is already reality? How would it look like? React's foundations are reactive rendering and UI as a pure function of state. These two foundations are reactive programming and functional programming, yet React has a lot of concepts from imperative programming. In this talk we will discover ho
Reactive MVC and the Virtual DOM
The web frontend scene is witness to many new frameworks and ways of working. It can be quite annoying when software becomes legacy quicker than ever. But actually, it's just good old innovation happening as it should, because the opportunities for improvement are there. Frameworks come and go, but what remains are the good ideas that they brought to the world. We're going to talk about the good i
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - cyclejs-community/cycle-webworker: A simple webworker driver for Cycle.js
GitHub - cyclejs-community/create-cycle-app: Create Cycle.js apps with no build configuration.
GitHub - TylorS/xs-dom: Experimental Cycle.js-specific Virtual-DOM Library.
GitHub - raquelxmoss/cycle-keys: A Cycle.js driver for keyboard events
GitHub - DerekCuevas/friend-list: A non-trivial (yet simple) front-end programming challenge.
Node server with Rx and Cycle.js
GitHub - pH200/cycle-react: Rx functional interface to Facebook's React
GitHub - staltz/mvi-example: A demo of the Model-View-Intent architecture with Virtual DOM renderer, for single-page apps.
An idea for scoping Cycle.js child components/dialogues in the context of their parent. Any driver can optionally supply a scope() function, which returns a scoped instance of itself. A driver can also supply an unscope() function which returns a transfor
Automatic scoping of nested dialogues · Issue #167 · cyclejs/cyclejs
GitHub - motorcyclejs/core: A fully reactive JavaScript framework for Human-Computer Interaction
How to request data sequentially in Cycle.js?
GitHub - Cmdv/cycle-webpack-boilerplate: cycle webpack babel boilerplate
Tiny Cycle.js 1