Live data from Hacker News

GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away

zendev.com

51–60 of 140 posts

Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away

#51

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…

I've tried Vue out and have pretty clear gains in productivity, personally. For me, it really zeroed in on the pain points of React.

Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away

#52

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…

To me, React also has the killer feature of being "generic enough" that I can see directly migrate-able variants of it still being used in ten years. The backend may change, but the basic setup of JSX -> function transpiling with param-attribute equivalency is simple enough to be a new foundational structure.

Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away

#53
post #35

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.

You can also look at job postings as another metric of popularity. Last I checked, Vue wasn't sought nearly as much as React.

As a recent job seeker (and attainer), I can attest. React is multitudes more in-demand from an employment perspective.

Re: GitHub Stars !== Usage: React Is Still Blowing Vue and Angular Away

#54
post #37

React is indeed the new jQuery.

Isn't Vue the new jQuery? Because you can drop it in so much easier

In usage, maybe. React is the "people are learning this instead of raw javascript" kind of default that jQuery became.

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

#55

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. Use whatever tool gets the job done.

> 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

#57

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…

> React (really JSX) solves the single problem of making HTML a part of JavaScript

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

#58

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…

This is pretty much exactly how I feel. There has been a lot of "anti-React" virtue signaling in the Javascript community over the past few years, and I just don't get it. Why is your whole front-end team switching from React to X, where React - X ~ epsilon? If it ain't broke, don't fix it. If you're switching from jQuery or templates to X, it is more reasonable, but I've seen teams rewrite Angular and React codebases in Vue (i.e. "we're hip and modern now").

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

#59

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…

I find the whole premise of putting the html in JavaScript bizarre and I think it is a passing fashion while the various debates around web components and shadow DOM isolation get sorted out.

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

#60

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…

> With React there's no weird "v-if ng-if" template logic that you have to grapple with.

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.

Post reply on HN