Flux vs Kendo UI

Overview

Flux

Stacks526

Followers513

Votes130

Kendo UI

Stacks297

Followers359

Votes33

GitHub Stars2.6K

Forks1.9K

Flux vs Kendo UI: 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.

What is Kendo UI? Fast, light, complete: 70+ jQuery-based UI widgets in one powerful toolset. Fast, light, complete: 70+ jQuery-based UI widgets in one powerful toolset. AngularJS integration, Bootstrap support, mobile controls, offline data solution.

Flux and Kendo UI can be primarily classified as "Javascript UI Libraries" tools.

"Unidirectional data flow" is the primary reason why developers consider Flux over the competitors, whereas "Collection of controls" was stated as the key factor in picking Kendo UI.

Flux and Kendo UI are both open source tools. It seems that Flux with 16.2K GitHub stars and 3.62K forks on GitHub has more adoption than Kendo UI with 2.16K GitHub stars and 1.73K GitHub forks.

Facebook, Hootsuite, and Tilt are some of the popular companies that use Flux, whereas Kendo UI is used by Oconics, Callision, and GripeO. Flux has a broader approval, being mentioned in 67 company stacks & 29 developers stacks; compared to Kendo UI, which is listed in 15 company stacks and 8 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Flux, Kendo UI

James

Lead Application Architect at TekPartners

Apr 13, 2022

Decided

Full disclosure; I worked for both Telerik and Infragistics in Developer Relations for these projects. From my point of view, neither is a clear "winner" in this space. Kendo has some nice features and Ignite doesn't have and vice versa. We ended up picking Kendo because we needed to settle on one of these, and most of our clients already owned Kendo because it came with some other Telerik product. That's it. It could have very easily gone the other way, but Telerik kinda won the ground war here, so...

Having said that, the only tool we really use is the grid (the rest of them are no better than Flowbite/HTML5/etc. controls. And even then, we really need to be leveraging the advanced functionality of the grid before telling the client they'll have to buy a support license.

16.7k views16.7k

Comments

Detailed Comparison

Flux	Kendo UI
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.	Fast, light, complete: 70+ jQuery-based UI widgets in one powerful toolset. AngularJS integration, Bootstrap support, mobile controls, offline data solution.
-	Ultimate Performance with Minimum Resources;Mobile-Friendly and Responsive;Built-In, Customizable Themes ;Open Source Core
Statistics
GitHub Stars -	GitHub Stars 2.6K
GitHub Forks -	GitHub Forks 1.9K
Stacks 526	Stacks 297
Followers 513	Followers 359
Votes 130	Votes 33
Pros & Cons
Pros 44 Unidirectional data flow 32 Architecture 19 Structure and Data Flow 14 Not MVC 12 Open source	Pros 15 Collection of controls 5 Speed 4 Multi-framework support 4 Mobile 2 AngularJS Cons 4 Massive footprint 3 Slow 1 Awdawd 1 Poor customizability 1 Expensive
Integrations
React	Bootstrap AngularJS

What are some alternatives to Flux, Kendo UI?

jQuery

jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.

AngularJS

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

React

Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

jQuery UI

Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice.

Svelte

If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads.

Famo.us

Famo.us is a free and open source JavaScript platform for building mobile apps and desktop experiences. What makes Famo.us unique is its JavaScript rendering engine and 3D physics engine that gives developers the power and tools to build native quality apps and animations using pure JavaScript.

Riot

Riot brings custom tags to all browsers. Think React + Polymer but with enjoyable syntax and a small learning curve.

Marko

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.

Preact

Preact is an attempt to recreate the core value proposition of React (or similar libraries like Mithril) using as little code as possible, with first-class support for ES2015. Currently the library is around 3kb (minified & gzipped).

Related Comparisons

"Unidirectional data flow" is the primary reason why developers consider Flux over the competitors, whereas "Collection of controls" was stated as the key factor in picking Kendo UI.

Flux vs Kendo UI