5 ms·
A small side track to the topic: I've been evaluating data querying, caching (or syncing) options for building modern JS apps. Public GraphQL solutons seem not
by dirtyaura 11y ago
A small side track to the topic: I've been evaluating data querying, caching (or syncing) options for building modern JS apps. Public GraphQL solutons seem not to be practical enough for fast prototyping yet, but redux looks a promising middle-ground. Have you done production apps on it? Any downsides?
- TheAceOfHearts 11y agoI'm currently in process of rewriting our work application from AngularJS to Redux. The downside with redux is that simpler things can take a bit more code than you might wish. You have to add an action handler / reducer, action creator, etc. However, it's generally very easy to extend previously written code, and it's very easy to reason about the data / logic flow. Another pitfall with redux is that it doesn't provide any help when you have to react to changes. A few days ago in reddit I wrote a small example explaining what I mean [0]. You might be interested in checking out relay-local-schema [1], it looks promising for experimenting with GraphQL and Relay. [0] https://www.reddit.com/r/javascript/comments/3u0167/getting_started_with_redux_a_free_30part_video/cxbg9s4 https://www.reddit.com/r/javascript/comments/3u0167/getting_... [1] https://github.com/relay-tools/relay-local-schema https://github.com/relay-tools/relay-local-schema