No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars. 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. React (really JSX) solves the single problem…
GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
51–60 of 140 posts
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#52No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars. 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. React (really JSX) solves the single problem…
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#53A 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.
You can also look at job postings as another metric of popularity. Last I checked, Vue wasn't sought nearly as much as React.
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#54React is indeed the new jQuery.
Isn't Vue the new jQuery? Because you can drop it in so much easier
I hope it does the same thing that jQuery did, and that is essentially make itself unnecessary in a lot of ways. Take all the really good features of React and make them browser-native.
To a certain degree, this is already happening. Web components are inching closer every day.
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#55Why 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. Use whatever tool gets the job done.
That's the problem: there are so many tools/frameworks/libraries etc. with so much overlap that people don't know what tool is for what job anymore. And there might not be a real answer to that. When you have a situation like this, people tend to use proxy measures like github stars to figure out what tool to use. Sure, it might not be the right tool, but it's at least picking a tool, as opposed to being locked in constant confusion about which path to take. Sometimes the right tool is the tool you have.
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#56Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#57No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars. 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. React (really JSX) solves the single problem…
The reason I like the way Vue works is because it makes javascript part of the HTML definition (with component definitions), essentially the opposite of what you like about React. That said, my use case of Vue is very different to my use case for React. Even though Vue does essentially solve the same problem set, their approaches have pros and cons in different scenarios.
(all that said I typically don't need to use either for what I do, in preference of light vanilla JS classes)
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#58No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars. 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. React (really JSX) solves the single problem…
In my experience, React's API has been far more intuitive than directive-based frameworks, and switching between the various directive-based frameworks seems like too much work for too little change. I would be interested in frameworks which aim to mimic React's API but offer more in terms of size (smaller is better) and performance. This is why I closely watch projects like Preact.
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#59No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars. 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. React (really JSX) solves the single problem…
I would hope my graphic artist will eventually be mixing 3 layers of HTML elements that seem entirely standard to him except the 3 different sources of docs.
Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away
#60No one I work with has ever even brought up the possibility of switching from React to Vue, let alone counting Github stars. 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. React (really JSX) solves the single problem…
Yes, I hate that syntax. It's like they picked the worst from HTML and Javascript. Instead "if" statements should be dealt with in Javascript entirely.
It's one of the reasons why I don't use Vue.