On top of everything that has already been explained in the previous comments, I will gladly…
jair orozco

Ah, I see now that I misunderstood. I didn’t realize you were just speaking in broad strokes in the arena of debating React vs. Vue; I was expecting/hoping you would be offering some elucidation relating to the specific technical limitations I described in the article.

I regard the framework debate as one that’s highly subjective and has been had too many times, and I honestly have no interest in participating in that exercise in futility. While I can definitely appreciate your passion and the points you raised, there’s one glaring discrepancy I would be remiss if I didn’t at least mention. You made reference to ReactNative repeatedly as though Vue has no offering in the realm of native development, but there also exists AliBaba’s Weex framework, which is the Vue-powered alternative to ReactNative.

People love to debate opinions until they’re blue in the face, but life’s too short. I don’t know why the opinions of everyone else matters so much to other people. If some people are in love with React in all its forms, that’s great. If others love Vue that same way, good for them too. If someone else hates or loves both, enjoy.

Thanks for the offer of help. I’m always appreciative to see experienced devs who are happy and willing to assist others. I’m actually already knee-deep into React work myself, amid a few other large-scale, long-term React-centric platform rewrites, which includes some heavy ReactNative development.

I actually like React a lot and use it extensively. I just also like Vue [albeit more]. The fact that I’m discussing a preference for Vue and some limitations I’ve come up against with React doesn’t make me anti-React, though it does clearly make me a pariah in the eyes of hardcore React-only developers for some reason.

C’est la vie!

Like what you read? Give Rommel Santor a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.