I don't think Vue is not capable of handling big enterprise-level projects. I have tons of projects done with Vue (actually Nuxt.js) and I will share them here on DEV.to once they are published.
I think you should try Vue as well.
BTW Vue also supports TypeScript (though I'm not a fan of xD) and also has Vuex (like Redux).
Coding in vue is more organized than in React. I think React is just-get-shit-done attitude. As you can see in this post, React lets us use raw javascript in rendering and binding events. Sometimes it feels more comfortable except when you have to bind inputs to states.
Hahaha, good explanation.
True! In React in case you want to handle a data change and use a two-way binding system you should have a function that is called through onChange event on the input and then update its state while Vue has an attribute (directive) called v-model and that's all what you need!
I don't think Vue is not capable of handling big enterprise-level projects. I have tons of projects done with Vue (actually Nuxt.js) and I will share them here on DEV.to once they are published.
I think you should try Vue as well.
BTW Vue also supports TypeScript (though I'm not a fan of xD) and also has Vuex (like Redux).
It is capable. if it's suitable, that's another question.
Coding in vue is more organized than in React. I think React is just-get-shit-done attitude. As you can see in this post, React lets us use raw javascript in rendering and binding events. Sometimes it feels more comfortable except when you have to bind inputs to states.
Hahaha, good explanation.
True! In React in case you want to handle a data change and use a two-way binding system you should have a function that is called through
onChangeevent on the input and then update its state while Vue has an attribute (directive) calledv-modeland that's all what you need!I think the choice of a framework is only a personal matter. Both Vue and React are great tools for designing web apps. They are both powerful.