One problem with JavaScript frameworks is that they're just one instantiation of a full spectrum of possible solutions. One solution isn't as universal as we might hope. Even a specification such as Flux that contains just a handful of patterns is open for interpretation. The fact that they're just patterns makes it easier for one group to go and implement their software one way, while another group uses the same patterns to implement their software how they see fit.
In this section, we'll reiterate the fact that Flux is just a set of patterns to follow. We'll revisit the possibility of using a Flux library, each of which has a different take on implementing the Flux patterns. Then we'll consider the trade-offs of implementing our own Flux components.