5 ms·

React is just for presentation though (the V in MVC)

Renaud 12y ago
But React + Flux is an alternative to MVC. Still early days for Flux, but the principles are sound and I hope it offers a viable alternative to all these framework that rely mainly on variants of the MVC pattern.
- Kiro 12y ago
  Flux seem so overcomplicated I can't believe what I'm seeing.
  - colinramsay 12y ago
    I think Flux is probably very simple, it's just been presented very, very poorly.
    - Kiro 12y ago
      Do you have any good tutorial that presents in a better way?
      - andwaal 12y ago
        Check out https://github.com/spoike/refluxjs https://github.com/spoike/refluxjs better explained and more elegant implemented( no string dirty-checking for one).
      - colinramsay 12y ago
        I agree with andwaal that reflux is the simplest way so far that I've seen. I think what is really lacking is a demonstration application which isn't just "hello world" or the standard todo app rewritten in React. I just don't find that helpful. For another overview, see this article: http://blog.andrewray.me/reactjs-for-stupid-people/ http://blog.andrewray.me/reactjs-for-stupid-people/ Please don't take offence at the title, I didn't write it :D
  - mercer 12y ago
    Perhaps Reflux is better for your purposes? https://github.com/spoike/refluxjs https://github.com/spoike/refluxjs
  - o_____________o 12y ago
    The overcomplication (relative to what could be) is due to boilerplate and poorly defined convention for anything but the canonical todo app. It's early days. There are some frameworks using some form of the Flux spec like Fluxxor and Reflux, but they're not opinionated or complete enough to hit the ground running. The author of Fluxxor, for example, is himself working out where to put very basic functionality like network service calls. In the react-router project, there's not an obvious way to either render from server or refetch data on route changes. This is all very basic functionality for a medium to large project. It will feel like you're in the weeds after a couple of days of development. We need a Flux++ framework with some stronger opinions, closer to Ember or Angular in scope.

But React + Flux is an alternative to MVC. Still early days for Flux, but the principles are sound and I hope it offers a viable alternative to all these framework that rely mainly on variants of the MVC pattern.

Kiro 12y ago
Flux seem so overcomplicated I can't believe what I'm seeing.
- colinramsay 12y ago
  I think Flux is probably very simple, it's just been presented very, very poorly.
  - Kiro 12y ago
    Do you have any good tutorial that presents in a better way?
    - andwaal 12y ago
      Check out https://github.com/spoike/refluxjs https://github.com/spoike/refluxjs better explained and more elegant implemented( no string dirty-checking for one).
    - colinramsay 12y ago
      I agree with andwaal that reflux is the simplest way so far that I've seen. I think what is really lacking is a demonstration application which isn't just "hello world" or the standard todo app rewritten in React. I just don't find that helpful. For another overview, see this article: http://blog.andrewray.me/reactjs-for-stupid-people/ http://blog.andrewray.me/reactjs-for-stupid-people/ Please don't take offence at the title, I didn't write it :D
- mercer 12y ago
  Perhaps Reflux is better for your purposes? https://github.com/spoike/refluxjs https://github.com/spoike/refluxjs
- o_____________o 12y ago
  The overcomplication (relative to what could be) is due to boilerplate and poorly defined convention for anything but the canonical todo app. It's early days. There are some frameworks using some form of the Flux spec like Fluxxor and Reflux, but they're not opinionated or complete enough to hit the ground running. The author of Fluxxor, for example, is himself working out where to put very basic functionality like network service calls. In the react-router project, there's not an obvious way to either render from server or refetch data on route changes. This is all very basic functionality for a medium to large project. It will feel like you're in the weeds after a couple of days of development. We need a Flux++ framework with some stronger opinions, closer to Ember or Angular in scope.