Need advice about which tool to choose?Ask the StackShare community!
Flux vs Marko: What are the differences?
Developers describe Flux as "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. On the other hand, Marko is detailed as "An isomorphic UI framework similar to Vue". Marko is a really fast and lightweight HTML-based templating engine that compiles templates to readable Node.js-compatible JavaScript modules, and it works on the server and in the browser. It supports streaming, async rendering and custom tags.
Flux and Marko can be primarily classified as "Javascript UI Libraries" tools.
"Unidirectional data flow" is the primary reason why developers consider Flux over the competitors, whereas "No JSX" was stated as the key factor in picking Marko.
Flux and Marko are both open source tools. It seems that Flux with 16.2K GitHub stars and 3.62K forks on GitHub has more adoption than Marko with 9.08K GitHub stars and 565 GitHub forks.
Pros of Flux
- Unidirectional data flow44
- Architecture32
- Structure and Data Flow19
- Not MVC14
- Open source12
- Created by facebook6
- A gestalt shift3
Pros of Marko
- Simplicity6
- Speed5
- Better than React, Vue, etc5
- No JSX5
- HTML markup4
- Components4
- Performance4
- Data Flow2
- Documentation1
- Low CPU cost1
- Virtual DOM1
- Isomorphic1
- Chut1
Sign up to add or upvote prosMake informed product decisions
Cons of Flux
Cons of Marko
- Extensibility1
- Unit test1
- Mobile native1