Vue is for noobs and back-end developers that don't know any better. There's no reason whatsoever to use it after you're familiar with React. Don't buy into the hype. There's lots of things that are intuitive or easy to learn in React, and have to be researched and memorised in Vue. Being a 'Vue' dev is a constant exercise in rote memorisation and remembering how things behave in certain edge cases.
Let me throw out an example I ran into 2 hours ago. I could do this basically any day of the past 6 months and give you a different example.
Say you need to render a component dynamically based on some data. Maybe you have the name of the component in a string (i.e it's come from a back-end etc) and know the scope it lies in, or maybe you're passed a component as a prop (you see this pattern all the time in higher order components in React, i.e '(Component) => <Component />')
In React, you can simply do the above. If you've been programming in React for a while you probably intuitively know that you can just do (Component) => <Component />, why? Because the JSX transform is trivial, and you can do it in your head.
When you render a component in React, you know that the '<Foo />' transpiles down to React.createElement(Foo). It doesn't matter how Foo enters the scope, whether it's imported at the top of the file (and therefore closured into your function) or comes in as a prop, it'll just work. As long as you're familiar with the Javascript language, you'll know this just works.
In Vue, it's not that simple. Because Vue components are all in this complex templating language, you need to look up how to do even slightly advanced things like this. There's always a 'Vue' way to do it, rather than a 'Javascript' way to do it. Or, as in this case, there's a "refactor your entire component to be a render function" way to do it, almost like an 'escape' to using actual JS, because the Vue templating language just isn't good enough to handle what you want it to do.
And god help you when you need to try and figure out the Vue way of doing something via Google instead of having an expert mentor on your team to help. Forget the official docs, they're garbage. And Vue (as well as React, to be fair) has the same problem PHP had 15 years ago, squillions of noobs have just flooded into the ecosystem and resources like Stack Overflow, chat rooms etc are swarming with "slightly experienced noobs" trying to help people a little bit newer than themselves. The quality of online resources is shockingly low. Even if you're an experienced front-end dev and know all the terminology and how to phrase your questions and search queries, there's no guarantee everyone else does, so you'll have to wade through 50 nonsensical answers to every problem you might run into. It's infuriating, inefficient, and soul sucking.
And, you know what, just in general I'd never recommend anyone switch front-end libraries unless you have literally nothing else to do. As far as your personal learning and career progression goes, it's always best to learn how to do something new. Failing that, it's sometimes good to learn a different way of doing something. But the absolute worst thing you can do is learn a different representation of the same way of doing the same thing. Vue and React are the exact same shit. You're better off learning the inner workings of one of them (try building your own, it's fun!) so you can bring that knowledge to the next trendy crap that comes along, rather than trying to learn all the trendy crap.