News for hackers. Stuff that matters.
Re:Why we chose Vue.js over React by caub on Sunday December 11, 2016 @11:39AM (#13151802)
I wonder why people need Redux, Using simply React is great and enough if you understand it well
Re:Why we chose Vue.js over React by exception_e on Sunday December 11, 2016 @12:31PM (#13152043)
React is just the UI piece of the puzzle. Here's a nice description of when to use Redux:

"[Redux is justified when] you have a piece of data that needs to be used in multiple places in your app, and passing it via props makes your components break the single-responsibility principle (i.e. makes their interface make less sense)" (https://github.com/petehunt/react-howto/issues/12#issuecomme...)

This comment was written for Flux, but it is completely applicable for Redux.

When building something non-trivial, there are other pieces you'll want to pull in with React such as routing, messaging, etc.

Re:Why we chose Vue.js over React by caub on Monday December 12, 2016 @10:47AM (#13158850)
Yea I know what Flux, Redux are, and honestly I think they are completely not needed if you understand and use React well, see comment below
Re:Why we chose Vue.js over React by ulisesrmzroche on Sunday December 11, 2016 @12:58PM (#13152171)
No it's not. You can't communicate cross components with just react, you're stuck on a parent-child relationship.
Re:Why we chose Vue.js over React by caub on Monday December 12, 2016 @10:46AM (#13158836)
you can by passing right state to the closest common parent. I pass props down, and a custom update function, easy, efficient (with PureComponents)