6 ms·
For a software project, library/framework choice is the most critical thing one must do. For the VueJS case, i did really want to adopt it for my projects, but
by revskill 7y ago
For a software project, library/framework choice is the most critical thing one must do.
For the VueJS case, i did really want to adopt it for my projects, but there's a fact that i'm not confident. They're not just "function".
And as i said above, in React case, they're moving away from "component lifecycles", so if i chose VueJS, i'll get stuck in that paradigm.
- jeremyjh 7y agoYou should try software engineering instead of chasing fads. You cannot go wrong choosing either framework.
- revskill 7y agoIt's about the HOW. How we think, how we code. Yes, you can't go wrong choosing one or another, but you can't change anything in your mind about software engineering.
- cuddlecake 7y agoHopefully, your mind can change when presented with new information.
- rymate1234 7y agoReact still has a "component lifecycle" -- it's just with hooks the way you interact with that lifecycle is different [1]. > Hooks are a more direct way to use the React features you already know — such as state, lifecycle, context, and refs. They don’t fundamentally change how React works, and your knowledge of components, props, and top-down data flow is just as relevant. And if you like functional components, VueJS has them as well [2] [1]: https://reactjs.org/docs/hooks-faq.html#how-much-of-my-react-knowledge-stays-relevant https://reactjs.org/docs/hooks-faq.html#how-much-of-my-react... [2]: https://vuejs.org/v2/guide/render-function.html#Functional-Components https://vuejs.org/v2/guide/render-function.html#Functional-C...
- alangibson 7y ago> library/framework choice is the most critical thing one must do This is officially trolling.