It's the anti-value of copying ideas. The original idea always win.
Thanks me for not using VueJS, as i know it copied idea from ReactJS mostly. But i know that when i use React, upgrading and refactoring is a no-brainer.
It's the anti-value of copying ideas. The original idea always win.
Thanks me for not using VueJS, as i know it copied idea from ReactJS mostly. But i know that when i use React, upgrading and refactoring is a no-brainer.
I like both React and Vue. I used React first, but I've used Vue for longer now. React introducing a new feature doesn't change anything about what makes Vue.js good. One thing I like about Vue.js is that basic data binding is a job that is done by the framework, instead of the programmer. Another thing that I like is that async methods are supported everywhere that methods are supported. So async mounted works great for data loading. We do not "know that lifecycle is a bad pattern". Its just a pattern, and implementations can be good or bad.
As for react, I don't think hooks are the end of the story:
And I have never had trouble using them.
I googled “lifecycle bad pattern. And found https://hackernoon.com/problematic-react-lifecycle-methods-a...
But I didn’t see it explaining why it is bad.
My comment is due to the fact that, the OP editor uses a lifecycle, which relates to me, on the fact that i DID NOT choose Vue.
Now i'm happy with ReactJS, Hook, Suspense, and more.
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.
> 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... [2]: https://vuejs.org/v2/guide/render-function.html#Functional-C...
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.
This is officially trolling.
What ever do you mean by this? Hooks are more ergonomic in some scenarios, react's class methods in others.
Great way to get started and experiment. Sure, once you want to do more, you'll want build tooling etc., but that initial ease is really compelling for someone who's learning.