nuclear-js

I like the idea of moving that arrow the way he does. Everything else was just less convincing. The real power of React is composable components that are easy to think about. I don't think the author really "got" this; if he was building "complex state machines ... and [mixing] multiple concerns in one component", he was just doing it wrong. I also don't love the idea of stores depending on each other. In my experience, it leads to hard-to-maintain tangled interdependencies, especially on the frontend. I actually tried to use Bacon.js as a Flux replacement because of the reactive philosophy (this article was a source of inspiration), and while it was nice, the purported benefits of Rx fell flat and store interdepencies remained a problem. Now, I use NuclearJS [0] to avoid store interdependency altogether. It's actually what I was trying t

I'm in the planning phase of porting a large C# application's frontend to React on Node (for isomorphism). Basically we'll have our main application server (in this case, .net mvc api, but think django-rest-framework) talk to a node server as well as the client, with the same REST api. The plus is very real separation of concerns (django does all data handling, business logic; javascript does all UI). The downside is having two server stacks. FWIW, I'm planning to use nuclear-js[1] for flux. And we're considering porting our .net code to django. [1] https://github.com/optimizely/nuclear-js