Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I get the feeling that React with the Redux/Flux architecture scales to Facebook-level complexity a bit better than Vue. Vue feels kinda like if you made plain React with setState a lot easier to use.

The complete separation of presentation and state with flux is a lot of work but starts to pay off when your data is used in many places and you can just connect any piece to the same global state and keep consistency. Or when you can make writing API interactions really easy with one middleware and from there your requests are done declaratively with actions.

I wonder what it's like to use Vue with Redux! Probably a bit weird given the two-way binding, where Redux is all about one-way binding and cycling every change through a global state transition. At first glance (revue, vue-redux) this seems awkward.

How does your team accomplish the stuff you would otherwise do with Redux? How do you do AJAX and how do you propagate that around? I suppose it's just like regular MVVM, all pretty isolated.



Just FYI, Vuex is the first party answer for a Redux solution for Vue.


Redux is just a fancy PubSub, you don't need it to scale. The main thing Redux got right was jumping on the React hype train. Don't get me wrong, I write React apps with Redux myself, but Redux is far from being a mandatory component.


You can totally use Redux, but conceptually Vuex is so similar that you may as well use that.

Also, Vue doesn't really have two way binding, just the v-model directive that is syntax sugar for handling an event to update component state.


I'm pretty sure 99.999% of websites don't require Facebook complexity. And even if you do require it, I don't see why Vue.js can't handle what Facebook does.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: