StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Business Tools
  3. UI Components
  4. Javascript UI Libraries
  5. Flux vs Svelte

Flux vs Svelte

OverviewDecisionsComparisonAlternatives

Overview

Flux
Flux
Stacks526
Followers513
Votes130
Svelte
Svelte
Stacks1.7K
Followers1.6K
Votes502
GitHub Stars84.6K
Forks4.7K

Flux vs Svelte: What are the differences?

Introduction

In this Markdown code, we will discuss the key differences between Flux and Svelte, two popular technologies used for building web applications.

  1. Purpose and Architecture: Flux is a design pattern that focuses on unidirectional data flow, separating user interface components from the application state. It uses actions to describe user interactions and updates the state of the application through a central store. On the other hand, Svelte is a compiler that converts declarative code into efficient JavaScript. It eliminates the need for a virtual DOM and shifts the heavy lifting to build time, resulting in faster and smaller applications.

  2. Learning Curve and Boilerplate: Flux libraries, such as Redux, require developers to learn a specific set of concepts and write a significant amount of boilerplate code to handle actions, reducers, and stores. Svelte, on the other hand, has a smaller learning curve as it follows a familiar HTML and JavaScript syntax. It also reduces boilerplate code by automatically updating the DOM through reactive assignments and reactive statements.

  3. Bundle Size and Performance: Flux applications, especially those using Redux, tend to have larger bundle sizes due to the middleware and additional libraries required. On the contrary, Svelte applications have smaller bundle sizes as the compiler optimizes the code during build time, removing unused parts and generating highly efficient JavaScript. This results in improved performance and faster load times for Svelte applications.

  4. Reactivity and Component Updates: In Flux, components subscribe to the state changes in the central store and update based on those changes. This can sometimes lead to unnecessary re-renders and performance issues, especially with deeply nested components. Svelte, on the other hand, automatically detects and updates only the parts of the DOM that need to be changed, resulting in better reactivity and optimized component updates.

  5. Tooling and Ecosystem: Flux has a wide range of tools, libraries, and extensions available in its ecosystem. It has been around for a longer time and has a larger community support. Svelte, although relatively new, is gaining popularity and has a growing ecosystem. While the tooling for Svelte is not as extensive as Flux, it offers a rich set of built-in features and a straightforward development process.

  6. Compatibility and Integration: Flux can be integrated with various frameworks and libraries, such as React and Angular, enabling developers to leverage its benefits in existing projects. On the other hand, Svelte is a complete framework itself and does not require additional libraries for its core functionality. It can be used independently or integrated with other frameworks through custom adapters or APIs.

In Summary, Flux and Svelte differ in their purpose and architecture, learning curve and boilerplate, bundle size and performance, reactivity and component updates, tooling and ecosystem, and compatibility and integration.

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)
or
Manual

Advice on Flux, Svelte

Máté
Máté

Senior developer at Self-employed

May 28, 2020

Decided

Svelte is everything a developer could ever want for flexible, scalable frontend development. I feel like React has reached a maturity level where there needs to be new syntactic sugar added (I'm looking at you, hooks!). I love how Svelte sets out to rebuild a new language to write interfaces in from the ground up.

311k views311k
Comments
Raj
Raj

Oct 10, 2020

Review

It purely depends on your app needs. Does it need to be scalable, do you have lots of features, OR it is a simple project with very simple needs - many of those parameters clarify which technologies will fit.

If you are looking for a quick solution, that reduces lot of development time, take a look at postgraphile (https://www.graphile.org/postgraphile/). You have to just define the schema and you get the entire graph-ql apis built for you and you can just focus on your frontend.

On frontend, React is good, but also need to remember that it is popular because it introduced one way data writes and in-built virtual dom + diffing to determine which dom to modify. Though personally I liked it, am recently more inclined to Svelte because its lightweightedness and absence of virtual dom and its simplicity compared to the huge ecosystem that React has surrounded itself with.

In all situations, frameworks keep changing over time. What is best today is not considered even good few years from now. What is important is to have the logic in a separate, clean manner void of too many framework related dependencies - that way you can switch one framework with another very easily.

3.76k views3.76k
Comments
Alex
Alex

Full-stack software engineer

Apr 25, 2020

Decided

Svelte 3 is exacly what I'm looking for that Vue is not made for.

It has a iterable dom just like angular but very low overhead.

This is going to be used with the application.

for old/ lite devices . ie.

  • android tv,
  • micro linux,
  • possibly text based web browser for ascci and/or linux framebuffer
  • android go devices
  • android One devices
125k views125k
Comments

Detailed Comparison

Flux
Flux
Svelte
Svelte

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.

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.

-
Write less code; No virtual DOM; Truly reactive
Statistics
GitHub Stars
-
GitHub Stars
84.6K
GitHub Forks
-
GitHub Forks
4.7K
Stacks
526
Stacks
1.7K
Followers
513
Followers
1.6K
Votes
130
Votes
502
Pros & Cons
Pros
  • 44
    Unidirectional data flow
  • 32
    Architecture
  • 19
    Structure and Data Flow
  • 14
    Not MVC
  • 12
    Open source
Pros
  • 59
    Performance
  • 41
    Reactivity
  • 36
    Components
  • 35
    Simplicity
  • 34
    Javascript compiler (do that browsers don't have to)
Cons
  • 3
    Event Listener Overload
  • 2
    Complex
  • 2
    Hard to learn
  • 2
    Learning Curve
  • 2
    Little to no libraries
Integrations
React
React
No integrations available

What are some alternatives to Flux, Svelte?

jQuery

jQuery

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

AngularJS

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

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

Vue.js

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

jQuery UI

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.

Famo.us

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

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

Marko

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.

Kendo UI

Kendo UI

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

Preact

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

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase