No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars.<p>Compare to when React came out, it was immediate consensus that we need to switch from Backbone to React. When Angular gained popularity, we did not have an urge to switch because it felt unclear what the scope and direction of Angular actually was.<p>React (really JSX) solves the single problem of making HTML a part of JavaScript. For me, it's game over, they have solved the problem or came close enough to where I'm comfortable staying in the React ecosystem for the rest of my career.<p>With React there's no weird "v-if ng-if" template logic that you have to grapple with. To me, Handlebars already gave me enough taste of how horrible and limiting maintaining template logic outside of components is.<p>Just my take. No desire to even download Vue and try it out, I don't foresee any productivity gains from it.
Not really big fan of articles like this. Why the need to compare and say this one has more stars, or is more used, etc.<p>I am thankful that we have these frameworks / libraries / modules that have greatly helped in our software development process.<p>At the end of the day, what matters is developer productivity, their happiness and satisfaction (regardless of the toolkit they use), and the overall value that their product brings to their intended target (outcomes).<p>P.S.
I use Vue, React, Angular, whichever suits the need of the client the most.
A lot of people using Vue just link Vue from a CDN and drop it in a webpage as a script, without using NPM. Does the stats account that fact? Sure you can do that with React as well, but you wont in production with JSX as one needs to compile it with node.js toolchain. Same for Angular. Vue usage is more like jQuery usage than React in practice.
People have wildly different views on what Github stars are. Some see it as a way to bookmark project you find interesting while other simply stars whenever they feel like the project is impressive.<p>Bottomline is: it's not a good metric, it's simply a way to see how "popular" something is and how likely it is that some random developer saw your project.<p>While anecdotal, I've starred Vue because I see it as a cool project and I've starred React as another cool project. In both case, I did toy projects with the frameworks and never used it in production. On the other hand, apache/httpd I did a lot of projects with and I did not give it a star yet.<p>In my opinion stars are not endorsement, they're a questionable way to measure how likely it is that your coworker have heard of a given project.
React ecosystem heavily encourages the use of build tools dependent on NPM package management.<p>Vue users are more likely to bypass NPM. They are often on-boarded with the gentler approach most familiar to those who "sprinkle in some jQuery" - Drop in a <script> tag and you are ready to rock. This approach is more likely to use a local file or from CDN.
Why do people care which framework "blows" the other one away? In my opinion, it literally doesn't matter at all and arguing over such things seems amateur.<p>Use whatever tool gets the job done.
I agree that number of use is a good factor when choosing a framework. But Vue has incredible tools, resources and community so don't let that get in your way. I've tried all three and Vue is just such a pleasure to use.
I think that Vue.js is on the ascendance. I mentioned this earlier. It is on track to exceed React.js if things continue in this fashion. Github stars are a reflection of interest.<p>I do worry that Vue.js is mostly one guy, you like to at least have a higher bus factor than one: <a href="https://en.wikipedia.org/wiki/Bus_factor" rel="nofollow">https://en.wikipedia.org/wiki/Bus_factor</a>
Appreciate !== vs !=, no type conversion on Stars and Usage in comparison.
Also, agreed. Would be more interesting to crawl all repos to see which have React vs Vue vs Angular for a more detailed understanding of usage.
Of course GitHub stars do not show usage, it shows interest. Considering Vue came later, we can also say its interest grew much faster.<p>There is no winner anyway, both React and Vue are amazing tools giving you the power to solve the same problem in different ways: building UIs.
MooTools is in wider use on the web than Angular, React, and Vue.js combined. <a href="https://w3techs.com/technologies/overview/javascript_library/all" rel="nofollow">https://w3techs.com/technologies/overview/javascript_library...</a><p>It's funny, to me anyway, that this post look at the developer/development side of things rather than the end consumers of apps/sites side of things.
One observation worth remembering: Enterprise usage would most likely be hosted locally / downloaded once per version and used by N internal projects.
After building two large applications using React, Redux, Redux Sagas, and Typescript, I feel burnt out. I'm honestly surprised Elm or ReasonML aren't more popular as they seem to provide all those aforementioned libraries in one go.
Vue, React and Angular (and many other frameworks) have enough critical mass that they aren't going away, and will continue to get regular updates. This, combined with how well the framework fits your particular use case and team, is all that matters. Why we focus on which one is "biggest" is beyond me. Biggest doesn't matter. Big enough does. Once a framework achieves that size, it can be considered for things other than personal toy projects, and all the other factors are what should guide your final decision.
I've never heard anyone say that you can do X in Vue much easier than in React. I've heard a bunch of people say that it's easier to learn than React, but I found React very very easy to learn anyway. Basically, I've not heard a convincing reason to look into Vue yet, so I haven't.<p>Also, people contact me about jobs involving React several times a week. I've never been contacted about a job involving Vue. Not once.<p>I'm sure Vue is good, but <i>shrug</i>, so is React.
Back when dinosaurs roamed the earth and we all walked to school uphill, everybody used Struts for server side page rendering.<p>And at least a half of them hated it. When something better came along they dropped it like a rock.<p>Usage is a poor predictor of future sucesses. If people ar rooting for someone else, people have already started turning on you.
One thing to think about is what is the motivation/incentive for someone to take a specific action. For me personally, I will "star" something that I find interesting AND I think I might forget how to find it again. Example: people might forget the exact name/repo for colors.js so they will be incentivized to star it, but no one will forget "apache".<p>That's why vue might gain more stars than the current dominant players (react and/or angular)
I had a friend say something that I think is a pretty good way to look at it. He said: "React is the blockbuster hit at the box office, while Vue is the critics' darling"<p>The big question is if it's good enough to replace what's already established. Things will probably equalize eventually, but by the time Vue overtakes, if it does, there will probably be some kind of new and shinier thing that intends to replace both of them.
I think using number of downloaded will also count number of build on each commit. Imagine if you have three branch in your repository, each push will rebuild the project (redownload dependencies). If you push three times a day it will download three dependencies three times.<p>Also, some project include their dependencies to VCS which only count once per build.
I was thinking what is the reason that Vue have more stars than React given it is not used more (perhaps in China it is). My guess would be that it's because Vue is more community driven than React. Vue is dependent only on community while React is dependent on Facebook & community. Therefore I believe Vue community share more excitement for the project.
Maybe star power is more of a sign of acceleration than usage. For example, if I have several projects in react, and then I start to move into Vue, it is not like I am going to convert my past projects over to Vue as well. I'll only be starting my future projects in Vue.<p>So that means more and more developers are beginning to get interested into Vue.
That's alright to me, I use vue in my own projects and react at work and while I greatly prefer one, I don't hate the other (anymore).<p>An aside note is that I wish there were fewer developers in this type of threads pretending that the abomination that is JSX makes react better than vue... which can use JSX just fine.
While we're talking about starring, here's a great webapp that lets you tag and organise your existing GitHub stars beyond the anemic official capability (filter by language)<p><a href="https://astralapp.com/" rel="nofollow">https://astralapp.com/</a><p>(I'm unaffiliated)
I for one measure my developer e-peen (used to get me real women interwebz dates) by how many stars my framework of choices uses. I am shocked and appalled by these findings.
While Vue fits my brain _way_ better, most companies use React. Why? Their decision makers feel safer. (FB backing)<p>This makes me reluctant to jump in and burn bridges.
I star plenty of things that might be crap, but have something interesting about them. Not saying that applies here, but some of my favorite libraries aren’t starred because I use them so much and have the page memorized. Stars are a terrible metric. For example, I don’t have Rails starred.