4 ms·
State management is more sane and easy to understand in vue. I'm build an extremely complex application with vue and pulling it off. The extra layers of complex
by shams93 8y ago
State management is more sane and easy to understand in vue. I'm build an extremely complex application with vue and pulling it off. The extra layers of complexity with react like having to use container components was too much cognitive load for me as a single developer building a very complex app that it was crash and burn for me. Vue's simple and clear approach wins for me over perhaps the power of a purely functional environment like react. I don't doubt that react is a powerful tool but the combined cognitive load of learning react and redux compared to vue and vuex was what caused me to go for vue, its clarity reduces cognitive load and enables you to focus much more on the problem domain than the learning curve.
- shams93 8y agoAlso the rate of breaking changes with react is pretty intense. While you can author react without a build tool, and I certainly am using webpack with vue myself, your same vue know how also works for spots where you may not have a build tool available, like freelancing updates to wordpress for people for side money. In those cases you're stuck sticking js into a CMS editor. But vue has you covered in all scenarios from the complex app with webpack and vuex to simple reactive code entered into a cms editor without the benefit of a build tool.
- fourseventy 8y agoThats a great point about the CMS use case!
- wolco 8y agoThe rate of change is the biggest issue. If you are not working with react day to day you are at a big disadvanage.
- poxrud 8y agoWhat breaking changes? React's API has been very stable. As of version 16 the entire core has been rewritten without breaking the API.
- richeyryan 8y agoCan you elaborate on the rate of breaking change? As far as I'm aware React's API has been backwards compatible for many versions at this stage. There have been deprecations introduced with React 16 but they don't come into effect until 17 which seems pretty reasonable.
- dmortin 8y agoThe question is if I want to learn one or the other which should I learn? Is React the better choice if I want to learn something which may also potenitally be useful when applying for new jobs?
- klodolph 8y agoThere are a bunch of factors at play for getting jobs but which web frameworks you know is typically far down the list, at least for the decent jobs.
- wolco 8y agoFor jobs Angular is best for corporate dev. React is a requirement for most new startups. Things change quickly though.
- majkinetor 8y agoThere are always bunch of factors. Its called 'context'. If you ask a general question, there is no context. So the answer is simple - use Vue, not React. Its way easier to on board and get you up and running, and mature enough that you can develop complex apps if you need that. Other people usually tell 'it depends', but that is just excuse for not being able to draw a line.
- jordache 8y ago>The extra layers of complexity with react like having to use container components was too much cognitive load for me Wait, Vue doesn't prescribe the notion of a component tree with top level / parent components being containers for stateless feature agnostic granular components? In that context, the concept of a container component isn't too hard to digest, and you can see how all the modern component oriented frameworks work similarly. So how does Vue differ in this respect? From my limited playing around with Vue, I'm pretty sure it prescribes to container components as aforementioned.