News for hackers. Stuff that matters.
Re:Why we chose Vue.js by hesarenu on Friday October 21, 2016 @02:51AM (#12758615)
React is very simple. You need to understand only its basic life cycle. Rest is just JavaScript.
Re:Why we chose Vue.js by askmike on Friday October 21, 2016 @10:57AM (#12760957)
I disagree as soon as you write more than a single nested child/parent component, that requires a different way of thinking (should I use state or props?). And that you can't "just uses react". You kind of have to use redux (or similar) as well as a bunch of other stuff.
Re:Why we chose Vue.js by mambodog on Friday October 21, 2016 @11:45AM (#12761357)
People keep saying you 'have to use redux' but I think that's hugely misleading to a large section of potential React users who don't need the highly complex state management that redux facilitates, and could get by just fine with setState+props.

I'd hope that people who are being exposed to this idea at least also get the chance to read 'You Might Not Need Redux': https://medium.com/@dan_abramov/you-might-not-need-redux-be4...

Re:Why we chose Vue.js by cageface on Friday October 21, 2016 @12:22PM (#12761714)
Amen to that. Seems like everybody is cargo culting Redux but really you can get pretty far with just React plus some wrapper components to hold state.
Re:Why we chose Vue.js by hesarenu on Friday October 21, 2016 @12:55PM (#12762125)
You don't need to use redux. But it's very useful to manage state. I went from using simple components to flux to redux all in same project. For me State management is a very part of client ui.