Angular was the first and original framework implemented in Ionic, so probably it's more mature than their Vue or React versions ... also the fact that you're more comfortable with Angular probably plays a role.
I learned Angular 1, never progressed to newer releases.
I learned Vue and React after that, but I'm a big Vue fan, not a React fan ...
React just makes the dev work way too hard on arcane stuff like preventing unnecessary re-renders - you need to do your hooks and "useMemo" and whatever else exactly "right", or you'll have horrible performance with too many re-renders. What's so interesting about that, I wonder ... a (frontend) dev should be able to focus on business logic and UX, not on these obscure details - Vue just takes care of all that low level stuff and lets you focus on what's important.
And, Vue does all that while not having a larger bundle size than React (smaller even I think) ... yeah, big big Vue fan here, React is not really for me, every time I see articles or discussions on how to do things "right" in React I think, what's all the fuss, Vue makes all that easy with it's reactive architecture.
(funny - Vue is in fact more "reactive" than React, what's in a name, lol)
Yeah well, React isn't a completely bad or useless concept, but in my opinion Vue makes a dev's life much easier ... in React communities I always see these hugely technical debates about HOCs and hooks and props and whatever, and how to prevent unnecessary re-renders, and so on and so on ... too much stuff which IMO the framework should take care of, but which React forces the dev to handle.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Angular was the first and original framework implemented in Ionic, so probably it's more mature than their Vue or React versions ... also the fact that you're more comfortable with Angular probably plays a role.
I learned Angular 1, never progressed to newer releases.
I learned Vue and React after that, but I'm a big Vue fan, not a React fan ...
React just makes the dev work way too hard on arcane stuff like preventing unnecessary re-renders - you need to do your hooks and "useMemo" and whatever else exactly "right", or you'll have horrible performance with too many re-renders. What's so interesting about that, I wonder ... a (frontend) dev should be able to focus on business logic and UX, not on these obscure details - Vue just takes care of all that low level stuff and lets you focus on what's important.
And, Vue does all that while not having a larger bundle size than React (smaller even I think) ... yeah, big big Vue fan here, React is not really for me, every time I see articles or discussions on how to do things "right" in React I think, what's all the fuss, Vue makes all that easy with it's reactive architecture.
(funny - Vue is in fact more "reactive" than React, what's in a name, lol)
Wow! I didn't knew that! Makes sense. TBH, I don't understand the needs that created react.
Yeah well, React isn't a completely bad or useless concept, but in my opinion Vue makes a dev's life much easier ... in React communities I always see these hugely technical debates about HOCs and hooks and props and whatever, and how to prevent unnecessary re-renders, and so on and so on ... too much stuff which IMO the framework should take care of, but which React forces the dev to handle.