score:416
redux author here!
i'd like to say you're going to make the following compromises using it:
you'll need to learn to avoid mutations. flux is unopinionated about mutating data, but redux doesn't like mutations and many packages complementary to redux assume you never mutate the state. you can enforce this with dev-only packages like redux-immutable-state-invariant, use immutable.js, or trust yourself and your team to write non-mutative code, but it's something you need to be aware of, and this needs to be a conscious decision accepted by your team.
you're going to have to carefully pick your packages. while flux explicitly doesn't try to solve “nearby” problems such as undo/redo, persistence, or forms, redux has extension points such as middleware and store enhancers, and it has spawned a young but rich ecosystem. this means most packages are new ideas and haven't received the critical mass of usage yet. you might depend on something that will be clearly a bad idea a few months later on, but it's hard to tell just yet.
you won't have a nice flow integration yet. flux currently lets you do very impressive static type checks which redux doesn't support yet. we'll get there, but it will take some time.
i think the first is the biggest hurdle for the beginners, the second can be a problem for over-enthusiastic early adopters, and the third is my personal pet peeve. other than that, i don't think using redux brings any particular downsides that flux avoids, and some people say it even has some upsides compared to flux.
see also my answer on upsides of using redux.
score:-1
as far as i know, redux is inspired by flux. flux is an architecture like mvc (model view controller). facebook introduce the flux due to scalability problem when using mvc. so flux is not an implementation, it just a concept. actually redux is the implementation of flux.
score:0
redux require discipline regarding to immutability. something i can recommend is ng-freeze to let you know about any accidental state mutation.
score:4
i prefer using redux as it uses one store which makes state management much easier compare to flux, also redux devtools it's really helpful tools which let you see what you doing with your state with some useful data and it's really inline with react developing tools.
also redux has got more flexibility using with other popular frameworks like angular. anyway, let's see how redux introduces himself as a framework.
redux has three principles which can introduced redux very well and they are the main difference between redux and flux also.
single source of truth
the state of your whole application is stored in an object tree within a single store.
this makes it easy to create universal apps, as the state from your server can be serialized and hydrated into the client with no extra coding effort. a single state tree also makes it easier to debug or inspect an application; it also enables you to persist your app's state in development, for a faster development cycle. some functionality which has been traditionally difficult to implement - undo/redo, for example - can suddenly become trivial to implement, if all of your state is stored in a single tree.
console.log(store.getstate())
/* prints
{
visibilityfilter: 'show_all',
todos: [
{
text: 'consider using redux',
completed: true,
},
{
text: 'keep all state in a single tree',
completed: false
}
]
}
*/
state is read-only
the only way to change the state is to emit an action, an object describing what happened.
this ensures that neither the views nor the network callbacks will ever write directly to the state. instead, they express an intent to transform the state. because all changes are centralized and happen one by one in a strict order, there are no subtle race conditions to watch out for. as actions are just plain objects, they can be logged, serialized, stored, and later replayed for debugging or testing purposes.
store.dispatch({
type: 'complete_todo',
index: 1
})
store.dispatch({
type: 'set_visibility_filter',
filter: 'show_completed'
})
changes are made with pure functions
to specify how the state tree is transformed by actions, you write pure reducers.
reducers are just pure functions that take the previous state and an action, and return the next state. remember to return new state objects, instead of mutating the previous state. you can start with a single reducer, and as your app grows, split it off into smaller reducers that manage specific parts of the state tree. because reducers are just functions, you can control the order in which they are called, pass additional data, or even make reusable reducers for common tasks such as pagination.
function visibilityfilter(state = 'show_all', action) {
switch (action.type) {
case 'set_visibility_filter':
return action.filter
default:
return state
}
}
function todos(state = [], action) {
switch (action.type) {
case 'add_todo':
return [
...state,
{
text: action.text,
completed: false
}
]
case 'complete_todo':
return state.map((todo, index) => {
if (index === action.index) {
return object.assign({}, todo, {
completed: true
})
}
return todo
})
default:
return state
}
}
import { combinereducers, createstore } from 'redux'
let reducer = combinereducers({ visibilityfilter, todos })
let store = createstore(reducer)
for more info visit here
score:15
one of the largest benefits in using redux over the other flux alternatives is its ability to reorient your thinking towards a more functional approach. once you understand how the wires all connect you realize its stunning elegance and simplicity in design, and can never go back.
score:17
flux and redux . . .
redux is not a pure flux implementation but definitely inspired by flux. biggest difference is that it uses a single store that wraps a state object containing all the state for your application. instead of creating stores like you'll do in flux, you'll write reducer functions that will change a single object state. this object represent all the state in your app. in redux you will get the current action and state, and return a new state. that mean that actions are sequential and state is immutable. that bring me to the most obvious con in redux (in my opinion).
redux is supporting an immutable concept.
why immutability?
there are few reasons for that:
1. coherence - store's state is always being changed by a reducer so it's easy tracking who change what.
2. performance - because it's immutable, redux only need to check if previous state !== current state and if so to render. no need to loop the state every single time to determined rendering.
3. debugging - new awesome concepts like time travel debugging and hot reloading.
update: if that wasn't persuading enough, watch lee byron excellent talk about immutable user interfaces.
redux require a developer(s) discipline through the codebase/libraries to maintain this idea. you'll need to make sure you pick libraries and write code in a non-mutable manner.
if you'd like to learn more about the different implementation of flux concepts (and what works best for your needs), check out this useful comparison.
after said that, i must admit that redux is where js future development is going to (as for writing these lines).
score:37
both redux and flux require a considerable amount of boilerplate code to cover many common patterns, especially those that involve asynchronous data fetching. the redux documentation already has a handful of examples for boilerplate reduction: http://redux.js.org/docs/recipes/reducingboilerplate.html. you could get everything you might need from a flux library like alt or fluxxor, but redux prefers freedom over features. this could be a downside for some developers because redux makes certain assumptions about your state that could be inadvertently disregarded.
the only way for you to really answer your question is to try redux if you can, perhaps in a personal project. redux came about because of a need for better developer experience, and it is biased towards functional programming. if you aren't familiar with functional concepts like reducers and function composition then you might be slowed down, but only slightly. the upside for embracing these ideas in data flow is easier testing and predictability.
disclaimer: i migrated from flummox (a popular flux implementation) to redux and the upsides far outweigh any downsides. i prefer much less magic in my code. less magic comes at a cost of a little more boilerplate, but it's a very small price to pay.
Source: stackoverflow.com
Related Query
- What could be the downsides of using Redux instead of Flux
- What is the core difference of redux & reflux in using react based application?
- What are the cases where Redux dispatch could change?
- What are the benefits of using thunk middleware in redux over using regular functions as async action creators?
- Redux saga: What is the difference between using yield call() and async/await?
- What is the best option to use redux actions when using redux hooks?
- What is the common way to handle successful REST POST operation in UI using React and Redux
- What is a robust way of rendering a dynamic quantity of React child components, using the Redux container component pattern?
- What is the correct way to do an async action using redux observable and firebase?
- What is the difference between using constructor vs getInitialState in React / React Native?
- What is the best way to access redux store outside a react component?
- Is there any downside to using .tsx instead of .ts all the times in typescript?
- What is the best way to redirect a page using React Router?
- Getting an error "A non-serializable value was detected in the state" when using redux toolkit - but NOT with normal redux
- I am using Redux. Should I manage controlled input state in the Redux store or use setState at the component level?
- What is the difference using react-router and the express routes.js
- What is the intention of using React's useCallback hook in place of useEffect?
- Can I view/modify the Redux store using Chrome Dev Tools
- What is the difference between using constructor vs state = {} to declare state in react component?
- What is the difference between Redux Thunk and Redux Saga?
- What is the benefit of using withStyles over makeStyles?
- What is the benefit of using styled components over css modules in Reactjs
- Error withRef is removed. To access the wrapped instance, use a ref on the connected component when using Redux Form
- What is the main difference between using React-Redux Hooks and React-Redux Connect()?
- Downsides of using two UI libraries in the same react project?
- What is the benefit importing React, {Component} instead of just React?
- What is the necessity of "export default connect" when you are connecting your react component to redux store
- How can I develop locally using a domain name instead of 'localhost:3000' in the url with create-react-app?
- What is the pros and cons of using Rails asset pipeline vs. webpack to hold assets?
- Is it possible to call a reducer function from another reducer function (within the same slice) using Redux Toolkit?
More Query from same tag
- problem with passing style to style props
- searchkit - how to pass props into an itemComponent component
- React-bootstrap component not stretching to the bottom of the page
- ES6 Merge two arrays (array contains another array inside) based on key Typescript or Javascript
- react increment decrement counts issue
- change input based on props or state in react
- Why my usestate hook value is not updating after onClick event with no error at all?
- Reading Axios Get params in Asp.Net MVC controller
- How do I dynamically create components from templates and data requested via an API?
- How to convert a json encoded php variable to a JavaScript JSON object in the same file
- How do I insert a Django template variable into a React script?
- How to integrate Javascript variable into ReactJS JSX style element
- react firebase - filtering firebase fetched items by user uid value
- Using document.classlist.remove in react
- How to apply styling for 3rd party css framework like bootstrap
- React Router doesn't change the component
- Webpack and babel-loader not resolving `ts` and `tsx` modules
- Merge object properties and assign sibling properties with different names
- Using JavaScript to create an animated counter with React.js
- React - Slide out component on unmount
- ReactJs: How to map an object
- React HOC class returns nothing
- react axios cros body empty
- Any attempt to access props in MDX component results in failed build, but dev works just fine
- How do use a piece of state in two different components?
- Why does react keep changing into an unecessary timezone I just want to create a date object with the same date in the string
- TypeError: Cannot read property 'methods' of null
- React JS - iterate through external JSON file to populate table
- My React Component breaks when I use this.state
- MaterialUI label text disappearing and can not change or choose dropdown menu elements