![Cover image for [COMPARISON] Angular vs Vue.js vs React.js - which one you should choose in 2020?](https://res.cloudinary.com/practicaldev/image/fetch/s--hmhkCxLL--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://thepracticaldev.s3.amazonaws.com/i/5usn9sxigc04146shauo.png)
This article was originally published at Vue.js vs React.js vs Angular
Since a few years, the popularity of different front-end frameworks grew...
For further actions, you may consider blocking this person and/or reporting abuse
I would try to say to explain it shorter.
Another compartment I can make is if we think about the old Server Side web and the new Client side web we can say.
A) React isn't necessarily "full with anti-patterns"
B) As a Vue developer since 2017 I started getting lots of job inquiries last year
I'll just stop there. Your "explanation" seems like so much FUD (fear, uncertainty, doubt) to me.
well at least this is how the things looks to me . :)
About react.. well not full :) just embraces a few.. :D my definition of full is more then 2.
I just simply see you do not know what you are talking about. :)
Maybe I don't, however this is the way I see it. As said I am not a frontend developer still this is the way I will choose a framework. Also keep in mind this depends on country from country. I am coming from a mostly outsourcing country however we do a lot of product development and I am not coming from an country with a lot of service or outsourcing for service development.. so this is also something to be aware of ;)
Nice way to put it :)
The no job argument is so BS. According to you, we should all work in retail?
theatlantic.com/business/archive/2...
well I do work in retail :D
Somebody said that React isn't framework but only library. I think that the bigger one who have all in one is Angular framework
Yes, angular have the router, http service, rxjs, pipes, dependency injection, etc... All built-in. You don't need to pick one from others repo. It's force a structure to your project. For that reason big companies usually choose angular. The point is that angular team will take care of all the stuff for your. You're able to build the entire application only using the tools provided by core angular team. You don't need to find side libraries and decide which one feats for your project. That's the point
What it has built in isn't what makes it a library or framework, it's whether you call React code, or React code calls your code. In the former case, it would be a library, in the latter case (which is indeed the case) it would be a framework
Yes, that's one definition of framework (the one I prefer, too) but not the one the React team follows.
For them Next.js or GatsbyJS are frameworks that are built on the React library.
The React team can follow whatever self-delusional definition they like I guess 😜
dev.to/dexygen/why-reactjs-is-a-fr...
Few points:
These "tests" are so skewed nowadays and dont tell you anything.
Did you use the new ivy renderer for the angular benchmark?
The ivy renderer is not production-ready. So I find fair not to include this time.
Fair enaough, but a little noteor something wouldve been nice
Angular 9 is the game changer when it comes to bundle size and so many improvements. Enterprise companies are moving to Angular and are already using it. When it comes to working with big teams and big projects, Angular is the way to go. A lot of the data shown here doesn't show the private usage of the Enterprise sector since the majority of them has it as private, which means the number for Angular usage shown here is smaller. Also a lot of the people using racr add some much shit to it that it almost becomes a framework
From my personal preference Angular is great for team work especially when you need to build something that has to last years. Being opinionated big library gives ease on maintaining especially for projects where team may change over the years. Perfect for enterprise scale projects.
Then on other spectrum there is Vue.js if you just need to get something done fast. It is really pleasure to work with.
Hopefully in 5-10 years when WebAssembly is truly mature we will be comparing frameworks in strongly typed languages like Blazor and C#.
Thank You for the wonderful post. I recently posted a blog on Blazor vs Angular vs Vue vs React - Which is the better SPA? Check out and I hope you like it. - zenesys.com/blog/blazor-vs-angular...
My experience is Vue can be more JavaScripty, and React is more TypeScripty, although the official language for both is JavaScript -- A guide to using TypeScript in Vue, with maximal VSCode IntelliSense
Angular isn't so bad. I do get some inspiration from it. But it seems to be ageing and losing to competition from the same company (Google), AngularDart and Flutter for Web...
I am going to try Svelte for one project and see how that will work out. I am super excited about it because Svelte looks pretty cool :) If anyone is interested I can write a post about it after the project will be partly finished and share my experience.
Great overview!
As a vue fanboy, I strongly disagree that they're all as easy to learn. I would argue vue is much, much easier than the others :)
React does kind of force you into a whole new way of thinking which does take time. And Angular is very opinionated.
I'm wondering how you ended up on 97kb, since the official documentation of Vue states that (gzipped, but still) it ends up around 30kb.
ref: vuejs.org/v2/guide/comparison.html...
React is way easier to learn!!