4 ms·

Used refluxjs for data flow. Inside the stores, superagent is used for request handling. React-router was used for routing.

• balls187 12y ago
  Once I finally grok'd the implementations of Flux, I found the it to be a decent layer ontop of ReactJS. Of the implementations of Flux, Reflux is pretty good, with less hassle of a centralized dispatcher, and extra boilerplate. What I don't get is that the `trigger` is essentially a store created action, which goes against the unidirectional data flow model.
  • dwg 12y ago
    I definitely found Reflux to be more understandable and easier to put into practice than Flux in general. They trade-off some purity and flexibility for simplicity. That said the stores and trigger method are definitely one of the rougher areas in the app. Thinking back, the stores were probably the largest source of bugs, but they also contain more logic so it's reasonable to assume they would have higher bug density. Reflux was a great stepping stone, but this is the area I would most like to refactor and/or spend more time on in future projects. Fortunately there's a lot of interesting work going on in this area right now.