4 ms·
I can't agree. I've never worked with people that don't understand a convention like "put actions in actions.ts and selectors in selectors.ts". Nor is that real
by bayesian_horse 4y ago
I can't agree. I've never worked with people that don't understand a convention like "put actions in actions.ts and selectors in selectors.ts". Nor is that really a big deal because Redux is very easy to refactor, it's just pure functions.
- andix 4y agoSure, they do that. But what do I do with a 5000 lines of actions and selectors that are all used somewhere, are all named somehow similar/unclear and only work in a specific combination/order, nobody remembers anymore?
- bayesian_horse 4y agoDo your job? I mean if it is that complicated, it has to have some purpose and value behind it, also you wouldn't be hired or tasked to improve it. With redux there is a good chance the actions and state are at least very transparent, for example when using the devtools. In my experience it's a lot harder to deal with mutable state in some context provider or something.
- bayesian_horse 4y agoActually with redux it is trivial to record, replay, even filter actions. That's one reason I like redux so much. I expect this functionality from any other state management solutions I encounter. Some others indeed do have this.