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
This post is a non-exhaustive quick overview of the so-called “unidirectional data flow” architectures. Not meant to be taken as a beginner tutorial, but rather as an overview of their differences and peculiarities. At the end, I’ll introduce a new architecture which deviates significantly from the others. This post assumes client-side Web UI frameworks only. TERMINOLOGY It would be confusing to t
Once in a while someone points out how ReactiveX (Rx) does not have means to avoid glitches. [1] [2] Glitches are temporary inconsistencies emitted by Observables. Consider this example: --a------b------c------d--------e-------- --1-------------2---------------3-------- combineLatest --a1-----b1-----(c1c2)-d2-------(e2e3)--- Events in parentheses happen “simultaneously”. In practice they happen at
ReactiveX: Duality turns your mind upside downModel-View-Intent and the Virtual DOM. Andre Medeiros. October / 2014 Used React for RxMarbles.com Just the 'View' in MVC. Not really. React components Have state (Model) Handle inputs to change state (Controller) Render JSX templates (Presentation) Contain lifecycle hooks for external purposes Are opinionated on where should state live A MESS Don't ,
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く