4 ms·

So you are getting downvoted because you are shitposting some off-topic stuff. I don't know why we have to talk about React in every thread about Vue. But I'll

So you are getting downvoted because you are shitposting some off-topic stuff. I don't know why we have to talk about React in every thread about Vue. But I'll respond anyway. 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: https://twitter.com/ryanflorence/status/1095455632335921152 https://twitter.com/ryanflorence/status/1095455632335921152

revskill 7y ago
Hooks of course is not the end of story. It's just an evolution of how we do UI/UX. 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.
billconan 7y ago
Ya, I also could not understand why lifecycle is bad, because not only vue has it, other frameworks, like iOS sdk also has this concept. And I have never had trouble using them. I googled “lifecycle bad pattern. And found https://hackernoon.com/problematic-react-lifecycle-methods-are-going-away-in-react-17-4216acc7d58b https://hackernoon.com/problematic-react-lifecycle-methods-a... But I didn’t see it explaining why it is bad.
- revskill 7y ago
  Lifecycle is not to be reused. Hooks could be reused and used everywhere you want.
  - jeremyjh 7y ago
    In Vue nothing prevents you from reusing a common function in or as a lifecycle method. I’m sure you think mixins are bad too, since Dan does, but you can also just use plain functions and bind this.
    - revskill 7y ago
      You're reusing a function, not a lifecycle.
- jeremyjh 7y ago
  The react community has decided reacts implementation of lifecycle methods has some downsides. Every pattern has pros and cons, which may play out differently in different implementations.

revskill 7y ago

Hooks of course is not the end of story. It's just an evolution of how we do UI/UX. 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.

billconan 7y ago

Ya, I also could not understand why lifecycle is bad, because not only vue has it, other frameworks, like iOS sdk also has this concept. And I have never had trouble using them. I googled “lifecycle bad pattern. And found https://hackernoon.com/problematic-react-lifecycle-methods-are-going-away-in-react-17-4216acc7d58b https://hackernoon.com/problematic-react-lifecycle-methods-a... But I didn’t see it explaining why it is bad.

revskill 7y ago
Lifecycle is not to be reused. Hooks could be reused and used everywhere you want.
- jeremyjh 7y ago
  In Vue nothing prevents you from reusing a common function in or as a lifecycle method. I’m sure you think mixins are bad too, since Dan does, but you can also just use plain functions and bind this.
  - revskill 7y ago
    You're reusing a function, not a lifecycle.
jeremyjh 7y ago
The react community has decided reacts implementation of lifecycle methods has some downsides. Every pattern has pros and cons, which may play out differently in different implementations.