You have to give reasons why one is better than the other based on your experience.
Lets begin the discussion...
For further actions, you may consider blocking this person and/or reporting abuse
Read next
Stop using express.js
Sebastian Wessel -
Build a Blog Website with Reactjs and Hygraph CMS
Mwendwa Bundi Emma -
6 Websites You’ll Love As A Developer
MedCode -
Weekly web development resources #152
Vincent Will -
Top comments (54)
I personally feel like there’s not a whole lot of reasons to argue between the two. It’s best not to get into the habit of claiming one is better than the other. They’re both two tools that are used to accomplish a similar goal. You’ve gotta love having options!
I like this
Vue, it's easier to learn, it has a proper separation between logic, markup and style and it has useful directives that makes it so you can iterate over arrays and show an element much easier than mapping an array and returning html.
Honestly almost all of the answers are going to be bias because we all have our personal preferences. I'm going to go with React for 3 reasons.
As a person with (some) expertise in React - and even more so - as a person who co-writes the new React docs, I can give you the definite answer to this question and end all discussion once and for all...
...
...
the answer is...
...
...
✨ Use whatever better clicks for you! ✨
For a detailed comparison, check this Vue's page. Even though it's biased towards Vue, it does offer more factual arguments than this type of discussion.
Also, look at the community:
These are the folks who will answer your questions or who have written courses and posts you will learn from. If you dislike how someone communicates or what values they believe in, it will be more difficult to follow their instruction, participate in the conferences, and so on.
Some folks bring up job market as another argument here. I never learned Vue but I passed three job interviews in it. The frameworks are not THAT different and learning one will be much easier once you know the other, even because you will have the vocabulary to google the tools/solutions you need. Other than that, most employers have coding tests available in another framework and understand that you will need to learn their stack anyway so you won't make significant contributions in the first weeks/months. Lastly, most companies have their own ways of doing things so it's not like if you know React perfectly, you won't be confused at a place that uses React - especially that oftentimes, you will deal with legacy code and patterns that were great a few years ago but they were never updated and now just look odd.
⭐️ PERSONAL (not-so-)HOT TAKE
If I were to choose what to learn if I were to restart my journey right now, I'd make sure that I deeply understand JavaScript. Many of the issues people attribute to React stem, really, from JavaScript and from how React was implemented in this context. Really strong JS fundamentals will for sure not hurt you anyway 😊
I haven't used React so I can't compare the two, but I did want to point out two aspects of Vue that really impressed me. They might help other readers make their choice.
I was able to introduce Vue gradually to an existing web app. This is much safer and predictable than rewriting everything from scratch.
I was pleasantly surprised by Vue's gentle learning curve.
Better for … ?
Given your last article
Let's create a market place where users sell stuff
a4akki ・ May 22 ・ 1 min read
neither may be the optimal choice unless hiring is the overriding concern.
Going forward eCommerce may tend more towards the server again.
As SPAs, React and Vue could be held back by their SSR hydration costs.
Hydration is Pure Overhead
Miško Hevery for Builder.io ・ Apr 20 ・ 13 min read
Back in 2014 eBay decided that React didn't meet their needs, leading to Marko
Making the world’s fastest website, and other mistakes
Taylor Hunt ・ Mar 15 ・ 9 min read
Another contemporary alternative is
Server-Side Rendering with Astro
Marko for Sites, Solid for Apps
Ryan Carniato for This is Learning ・ Apr 25 ・ 7 min read
Vue is better at being green and react is better at being blue
In fact, react doesn't even try to be green which is the type of Idealism I prefer therefore it's the superior framework
I would say React:
But if you have a luxury to choose one for your next project, i would go with the one that you never worked before and learn a new skill.
Vue might be the best choice if you're a newer developer and not as familiar with advanced JavaScript concepts, while React is quite well suited for experienced programmers and developers who have worked with object-oriented JavaScript, functional JavaScript, and similar concepts
I don't have a vote, but as someone who has used React lightly, I have always browsed Vue's frameworks and tooling with interest. For example, I was surprised with all the money that Facebook poured into React and JS, that the Vue community ended up creating Vite.
I personally prefer the right tool for the job
Vue, because real reactivity, slots, router, pinía, v-model, better component structure, composables, real component life cycle, etc... And it's more easily to use and learn.
use effect = useShootOnMyFoot :v
I think this decision could be different for each case. Both libs are great and both resolve almost anything you'll need on a frontend software development.
But as I said, the decision could be different as in a team where do you have to understand which are the pros and cons to use it, based on team experience. If it was a solo project I think that the lib that you have the most experience is the better.
React is cool, but I'm tired of React. Vue is nice, but I don't want to learn in. React makes me annoyed and frustrated at frontend. There's something about JSX that seems... disconcerting, if it's the best word. React makes me dislike frontend, although I'd probably always use React for frontend. Vue sounds nice, but I don't have motivation to learn it, so there, I just said nothing.
Both good, but if you choose Vue please use script setup everything older is ugly.
And I think this was part of Cues strengths and is now a failing. You have the old school Options API which I liked as there was less ceremony the new(er) config setup() and then
It makes it harder for new developers to be productive and relies on a toolchain.
script setup is less code I'm not talking about config setup() and it is close to vanilla html SFCs there is nothing hard about it or complicated. Options API is just not good, but of course people who learned it one way first will always be the first to complain.
I will always go for Vue. It's really easy to work with and has almost everything you need. Also it's very beginner friendly and highly scalable.