These are chat archives for jdubray/sam
The Flux-Challenge might be something to look at to get a feel for how the reactive loop is being handled without SAM. It is a repo with submissions using different frameworks to try and solve the challenge.
Here is the stated purpose of the challenge:
"This challenge is meant to be solved with Flux or some variation of this architecture, such as architectures with the single state tree and "actions" (Om, Redux, etc). It's my personal belief that Flux does not provide an elegant way of coordinating multiple async data sources, but more experienced Flux users might disagree. This challenge's requirements were tailored to touch Flux's weakest spots, these are not typical web app requirements. On the other hand, analytics and sensors dashboard UIs resemble this challenge a lot. That said, I am open and curious to be proven wrong about Flux. I'm curious about every solution's pros and cons, and I would prefer to discuss over evidence/artifacts instead of with platitude arguments."
Here is the link to the submissions page that also lists the libraries used with each submission made: