3 ms·
I'm an experienced web dev, who mostly works with Vue. Sometimes I have to work on React apps. Skimming through the list of sins, pretty much all of them look
by stevage 2y ago
I'm an experienced web dev, who mostly works with Vue. Sometimes I have to work on React apps.
Skimming through the list of sins, pretty much all of them look like things I do on a regular basis. I do not understand React. I find it pretty much incomprehensible, incredibly complicated, and overly complicated for what it does.
I can't really described what `useEffect()` does, only that it's a solution I use when other things don't work. I can't tell you when I should use `useRef()` rather than state or props.
I never have any of these issues in Vue. Its conceptual model has always been pretty easy to grasp, although it got messier in Vue 3 since they tried to copy React more.
- deweller 2y agouseEffect() replaces component lifecycle hooks in Vue. useRef() is the answer to this.$refs in Vue. Agreed that Vue and React are very different flavors. I think Vue has a shallower learning curve. In spite of React's problems, I do feel it scales to larger apps a little better than Vue. Both are great solutions.