redux

Agreed. There's currently about 2200 repos that show up in a Github search for "redux" + Javascript, and the vast majority of them are boilerplates, TodoMVCs, and copies of the "Full Stack Redux" voting tutorial. Have to admit I'm curious to see some bigger examples as well. The "Who Uses Redux?" issue in the repo ( https://github.com/rackt/redux/issues/310 ) does list a number of companies, so it does seem like there's actual usage. I also ran across https://github.com/mezod/listlogs/tree/joan , which is at least more of a real app. Finally, the Firefox DevTools now appear to use Redux some as well ( https://hg.mozilla.org/mozilla-central/rev/17d1d8bbae99 ).

To me the biggest problem with web development is, not that it's too big. I feel the information is really disorganised. For instance, take most of the front-end projects; finding good documentation is a fool's errand. I think we as a community need to put more effort in to making our projects easier to understand, we need to bring the barrier to entry as low as possible, we need to stop making assumptions that everyone starting out with our projects are people with 5-6 years experience, help people figure out where to look for information related to our project. For example, a good project I really appreciate is, redux; the documentation that comes with the project is really amazing, I mean look at this, https://github.com/rackt/redux/blob/master/README.md They have put so much effort in to making their project really easy to understand.

> anyone who really wants to hop on the FRP bandwagon will pick up something like http://elm-lang.org in order to fully achieve Satori Or you could just use React with Redux, like many people are doing! :) https://github.com/rackt/redux#influences

I personally like React + Immutable.js (for the store) + Redux (https://github.com/rackt/redux) which is more similar to Om and apparently Elm. It's actually the first Fluxlike implementation I willingly use.

1. If you're not passing the backbone models to React components, this sounds fine. backbone models as props ends up being really painful because of how mutable they are, and when we tried to manage that with mixins, it was buggy and caused problems (note: I'm not familiar with the actual mixin we used there and whether there was a better way to do it). Since most flux implementations are pretty stateful/mutable themselves, using mutable backbone models there, so long as you copy data out to pass to react views, seems safe. Though I'm excited long-term about the immutable flux implementations (https://github.com/rackt/redux) 2. We had a library originally written by Ben Alpert (now core react team) that handles all of our interactive svgs [1]. Since KA has a lot of legacy code there, and there hasn't been an immediate benefit to porting i

That should be possible! Of course, stateless components don't have state, so you would need to something like Recompose if you need that. And of course, not all React-related projects explicitly support stateless components at the moment (e.g. hot reloading). Another option is to use psuedo-local state with Redux and pass everything as props: https://github.com/rackt/redux/issues/159. As Dan notes in that issue though, it might be better to wait for the state tree model to be improved: https://github.com/facebook/react/issues/4595. In short: early days, too early to tell what patterns will emerge.

I think if you take a lot at the motivations that Dan Abramov had for creating Redux [1], you'll see that improving debugging was at the centre of it. Check out his talk he gave at React-Europe. He basically is talking about improving developer tools. The functional approach Redux takes allows for you to see state transitions and replay actions - making it relatively trivial (compared to say Angular.js) to understand how to reproduce a buggy state. [1] https://github.com/rackt/redux [2] https://www.youtube.com/watch?v=xsSnOQynTHs

More: http://stackoverflow.com/questions/32461229/why-use-redux-ov... Src: https://github.com/rackt/redux

Another commenter mentioned it, but I'm going to +1 using Redux [0] as well. If you need to pick up a framework, Redux is a great choice to consider, it's tiny and very simple. It pushes you towards keeping a lot of your business logic as pure JS, so testing your code tends to be really easy (and it means your code is re-usable, it's not tied super tightly to X or Y framework!). If you use it with React it's also a joy to test. Something that Redux doesn't solve is data fetching, caching, and mutations. If you have a reasonably sized application, you'll end up having to implement a lot of logic surrounding data fetching and caching by yourself. The suggested solution is to store your resources normalized, indexed by id, and create selectors to get the data in the shape you want. This works out alright, but it's tedious and during your fir

React + Redux: https://github.com/rackt/redux You will not regret it.

Always good to see alternatives to "Flux classic" [1]. We have just started using Redux [2] with ImmutableJS. It's a nice way of expressing how different actions mutate the store, but I do feel like there's some leaky abstractions in there - e.g. ImmutableJS is usually used for performance reasons, yet you see your entire app filled with getter boilerplate to get the data from the immutable structures. I have to say I don't quite see the difference between CSP used here and normal eventemitter style code. Can someone explain the difference? [1] https://github.com/facebook/flux [2] https://github.com/rackt/redux

Nice. I love Redux + React so much, so I appreciate any effort into making people more aware of it. I was really excited that you found a way to return proper 404's! https://github.com/GetExpert/redux-blog-example/blob/master/... There are a few things I would have done differently though. Check out: - this sample project I made. it's not ideal though and I have learnt a since I made this, but it has a few good ideas https://github.com/joshhunt/reactapus - the official 'real world' example https://github.com/rackt/redux/tree/master/examples/real-wor... Suggestions: - Consider putting client, server, and universal code into seperate folders like in my example - it makes it easier to understand what code is executing where. - Move routing into a 'universalRouter.js' which is the one place that performs routing and returns the root component

Just use redux, you won't regret it. https://github.com/rackt/redux