4 ms·

I've had the same experience. It took me about a week to "get" Redux as a new-ish dev back a year or so ago. Why do you think people have trouble with it?

ashark 10y ago
I've found it really easy once I stopped thinking about it in the way it's presented at all. The use of the term "action" is especially misleading. Easier to think of it as two event dispatchers hooked together (which is more or less what it is).
throwaway2016a 10y ago
> It took me about a week to "get" Redux You hit the nail on the head. Devs these days get frustrated if it takes more than an hour.
clay_to_n 10y ago
I think the different parts are confusing. As a dev learning about it for the first time, "Action Creator", "Store", and "Reducer" don't mean anything. Is "Store" a database connection? "Reduce" sounds like functional programming, sounds hard. Why "Action Creator"? Aren't actions objects that I can create with "new"? For me, I also didn't understand the value in splitting it into those pieces - when I was learning Redux, I kept wondering "why aren't these just pub / sub events? Can't you do this with an event bus?" I think most devs aren't used to learning new high-level patterns. Most know MVC, maybe a couple others, but I think Flux / Redux are a bit more complicated (by nature) than that. I doubt anyone interested in Domain-Driven Design or Clean Architecture would have an issue picking Redux up, but those devs are the exception.
lawik 10y ago
I watched a talk at a meetup on Redux. Loved the idea. Tried to try it out with React or Vue and had a lot of trouble getting going. I'm still fond of Redux as a concept but I've mostly had trouble trying to get the rest of my needs met. I'll try again at some point.
rickyc091 10y ago
I don't think people are having problem with understanding how redux work, but having problems with the shear number of boilerplate files you have to write to get anything done. Often times the speed at which you can get things done is equated to productivity.

ashark 10y ago

I've found it really easy once I stopped thinking about it in the way it's presented at all. The use of the term "action" is especially misleading. Easier to think of it as two event dispatchers hooked together (which is more or less what it is).

throwaway2016a 10y ago

> It took me about a week to "get" Redux You hit the nail on the head. Devs these days get frustrated if it takes more than an hour.

clay_to_n 10y ago

I think the different parts are confusing. As a dev learning about it for the first time, "Action Creator", "Store", and "Reducer" don't mean anything. Is "Store" a database connection? "Reduce" sounds like functional programming, sounds hard. Why "Action Creator"? Aren't actions objects that I can create with "new"? For me, I also didn't understand the value in splitting it into those pieces - when I was learning Redux, I kept wondering "why aren't these just pub / sub events? Can't you do this with an event bus?" I think most devs aren't used to learning new high-level patterns. Most know MVC, maybe a couple others, but I think Flux / Redux are a bit more complicated (by nature) than that. I doubt anyone interested in Domain-Driven Design or Clean Architecture would have an issue picking Redux up, but those devs are the exception.

lawik 10y ago

I watched a talk at a meetup on Redux. Loved the idea. Tried to try it out with React or Vue and had a lot of trouble getting going. I'm still fond of Redux as a concept but I've mostly had trouble trying to get the rest of my needs met. I'll try again at some point.

rickyc091 10y ago

I don't think people are having problem with understanding how redux work, but having problems with the shear number of boilerplate files you have to write to get anything done. Often times the speed at which you can get things done is equated to productivity.