Flight vs Flux: What are the differences?
What is Flux? Application Architecture for Building User Interfaces. Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.
Flight and Flux are both open source tools. It seems that Flux with 16.2K GitHub stars and 3.62K forks on GitHub has more adoption than Flight with 6.64K GitHub stars and 588 GitHub forks.
Facebook, Hootsuite, and Tilt are some of the popular companies that use Flux, whereas Flight is used by Adtena, Birchbox, and Drip. Flux has a broader approval, being mentioned in 67 company stacks & 29 developers stacks; compared to Flight, which is listed in 4 company stacks and 3 developer stacks.
What is Flight?
What is Flux?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Flight?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Flight?
What are the cons of using Flux?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Flight?
We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.
But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.
With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.
"Idiot proof MVC" using transactional pub/sub between models, views, and controllers to establish reliable one-way data flow. Combines well with Polymer web components to create a modular, loosely coupled front-end architecture.