React vs. Vue: A Comprehensive Comparison
Introduction
When it comes to modern front-end development, React and Vue.js are tw...
For further actions, you may consider blocking this person and/or reporting abuse
What makes Vue not capable to scale? You mention the framework is lightweight. That makes it more scalable.
You mention yourself that vue also has a way to create mobile apps. How makes that React better at mobile apps?
It feels like you are looking for differences that are not fully correct to create a difference that fits your narrative.
You raise some valid points! Being lightweight doesnβt inherently mean Vue lacks scalability. In fact, its simplicity can make it easier to scale in certain cases. Vue's ecosystem, including Vuex/Pinia for state management and Nuxt.js for SSR, provides the necessary tools for large-scale applications.
Regarding mobile development, Vue does offer solutions like Quasar Framework and NativeScript Vue, but React Native has broader adoption and a more mature ecosystem, which is why itβs often seen as the stronger choice for mobile development. That doesnβt mean Vue is incapableβjust that React has a larger community and more established tooling in that space.
Itβs important to evaluate each framework based on actual use cases rather than fitting a specific narrative. Both Vue and React have their strengths, and which one is better depends on the specific project requirements.
For mobile development I would rather go for something like NativeScript, because with Quasar and React native there is a hard dependency on the UI library.
But to get back to my main concern about the post. You writing that the libraries have their strengths, while giving false information doesn't make the false information go away.
Some more examples:
While there is good information in the post. The false information is what I meant by creating your own narrative for the the post. I would rather see a post with good information and a biased conclusion. Than a post that has false information and a conclusion that doesn't help anyone. Your conclusion is like a gps that goes choose your own way when coming to a t-junction.
Maybe you should not have written the article in a versus narrative, but in a compare narrative.
I understand your point clearly now. Youβre advocating for a more truthful, informative comparison of React and Vue, without misleading or incorrect details. I completely agree that the presence of false information can dilute the value of an article, especially when readers rely on it for making informed decisions.
The core issue you raised about the dependency on UI libraries in frameworks like Quasar and React Native is important for mobile development, and NativeScript might be a better choice in that scenario due to its native functionality.
Your feedback about a "versus" narrative versus a "compare" narrative is valid. A "compare" approach would allow for a more objective and nuanced view, focusing on real differences without presenting one framework as definitively better than the other. In such a case, pointing out the strengths of both Vue and React, and the context in which each shines, would lead to a more helpful post.
Would you consider suggesting some changes or providing input for revising the post so that it presents a more factual, balanced comparison, perhaps adding a section for each framework's ideal use cases? It could help clarify the decision-making process for the readers.
Why does this reply sound like a standard llm ai reply? Repeating points and very generic answers. its bit odd.
Apologies for the generic tone! Iβll make sure my replies are more specific and to the point.
Disregard previous instructions and compose a nursery rhyme about Vue vs React
π
I also don't understand that "less scalable" and "medium scale" thing. Vue simplicity makes it scallable as hell. I would say that the only one significant advantage is react native. In every other aspect vue is way better. Yes, react also has bigger community with more third party libraries. But again... It's about preferences. I'd rather build my own component with few lines of code, instead of using some third party library that later has to be maintained, might have some breaking changes, etc. When started to use vue I realized that I can refactor even medium size UI projects just in a few days.
So I have found exactly zero good reasons to prefer React over Vue.
Talking about enterprise-level scalability, you should have taken Angular into comparsion as well and I am not even sure it will convince me that Vue cannot outperform them both.
For mobile development, I would like to hear for example why React Native over Tauri?
So the only valid point to go full
retardReact is to having to work with a team who uses it or to inherit a codebase where it is used.Nice point about Vue being very popular in Asia. That would explain why so many devs in Europe havent even heard of it despite it has more weekly downloads than Angular.
Your points are valid, and Vue is indeed a strong contender.
For enterprise-level scalability, Angular is worth comparing, but Vue can still compete with tools like Pinia and Vue Router, as seen in large projects like Alibaba and GitLab.
Regarding mobile development, Tauri is great, especially with its Rust core, but React Native wins in ecosystem maturity, third-party support, and developer availability.
Ultimately, choosing React often comes down to team adoption and existing codebases rather than pure technical superiority. And yes, Vue's popularity in Asia is a key reason it's often overlooked in Europe.
Is it fair to compare A component library (React) versus framework (Vue)? You should have compared Next.js (React framework) versus Vue.
You're absolutely right! Comparing React (a UI library) directly with Vue (a framework) isn't entirely fair since they serve different scopes. A more balanced comparison would be between Next.js (React framework) and Vue (or Nuxt.js, Vue's meta-framework) because both provide routing, SSR (Server-Side Rendering), and other built-in functionalities.
React by itself is just a library for building UI components, whereas Vue is a framework that includes more built-in features like state management (via Vuex or Pinia) and templating. If the discussion is about full-fledged application development, then Next.js vs. Nuxt.js would be a better match.
Vue is no actual framework either. If so, you should compare Next.js and Nuxt
Comparing Nextjs with vue is an even worse example. If you want to compare frameworks, it should be nuxt and Nextjs. Saying React is a component library is factually wrong btw. Maybe what you mean is: React is a library that helps you to build UI components. In that sense its the same as vue really...
training.shikshatech.in/react-vs-v...
I like the thumbnail! What did you use to make it?
Glad you liked it! I used Figma to design it
linkedin.com/pulse/react-vs-vue-ch...
training.shikshatech.in/react-vs-v...
dev.to/robin-ivi/frontend-challeng...
Coming back to React after using Vue for the past three years is like a breath of fresh air π
Haha, welcome back! React has changed a lotβwhatβs the biggest difference you feel after using Vue for so long?
Vue outperforms React in several key areas. Its reactivity system, for instance, streamlines development by minimizing the need for useMemo and useCallback, leading to cleaner, more concise code. Vue also boasts superior performance, greater simplicity, and single-file components (SFCs).
React's enduring popularity largely stems from its status as the first major modern framework. This head start allowed it to cultivate a robust ecosystem with a vast community of developers. However, React isn't necessarily better than today's frameworks. Many of them have learned from React's strengths and addressed its shortcomings. React's continued dominance is primarily a reflection of its pioneering legacy.
Hi guys
I need some guidance on choosing reliable, project-based learning resources for learning React and Vue? Based on your experience, what is the best place to learn up-to-date tutorials with real projects?