I would stay with Vue. While the react world is bugger it's mostly made up of competing solutions instead of distinct tasks.

That said, this healthy Vue/Angular/React competition has been great for us devs.

"great" is relative to how much free time you have evaluating all the various alternatives and finding the bugs/missing use cases nobody cares to tell you about up front..

> the bugs/missing use cases nobody cares to tell you about

In the case of fewer frameworks, you would still have these. Arguably more due to lack of competition.

> evaluating all the various alternatives

Pick one of the "Big 3" above. You'll be fine. Largely due to the previous point.

I agree that competition is generally good, but I hate choices so much. I don't even care if Vue is 10 times better than React, I've just spent the last year diving into React and React Native. I've finished 3 big projects and now I'm feeling more confident. And now I get the feeling that I have to throw out a whole bunch of experience and switch to the next big thing.

I think I'm going to dig in my heels this time. React is fine. It's more than fine, I absolutely love working with React, Redux, redux-saga, redux-observable, and a whole bunch of other libraries and patterns that I've finally begun to master after over a year of headaches and frustration. I'm not going to switch to Vue, not even for my next side project.

I didn't personally care about the BSD+Patents license, but you definitely have to keep your eyes and ears open with backlash like this. Even if I think it's a total issue, it might affect my ability to hire employees or even sell my company. So I'm really glad that React is now released under the MIT license.

I don't think anyone's really claiming that Vue is a 'next big thing' to switch to from React. Vue/React/Angular are all competitors of the same generation.

> over a year of headaches and frustration

Seems like an argument against the react ecosystem

A thousand times this. We'll know the JavaScript UI toolkit has started to mature when we can pick up a new tool and not have to abandon all of the other tools we already learned and spend a year getting on our feet in a new "ecosystem".

Don't get me wrong, it was the good kind of struggle where you grow and push yourself. Like going to the gym.

It was the same as any other programming language, framework, or ecosystem. Exactly the same as my experience with Ruby on Rails when I first started doing web development.

If you don't mind sharing, what problem did you have before that was solved by adopting React? (I'm not referring to React Native. It's obvious to me what problem that solves.)

The main thing is having the state flow top-down through your app, so you never have to worry about manually keeping things in sync in the UI. Redux and redux saga have really taught me a lot about programming, and then RxJS and redux-observable completely blew my mind.

I've never found manually keeping things in sync with the UI to be overly burdensome. I guess I've just been lucky.

Many things going forward will happen in reacts petri dish. Lots of ideas seeking to get consensus like the evolution of styles, animations, native performance, async scheduler, easy-to-create native renderers. Vue is nice and all, but it's rather complacent, catering to old Angular-like roots and web artefacts. If you believed the hype then Vue was supposed to be the be-all-end-all of frameworks, the reality of course is quite sober: http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular...

The point has been made before that npm downloads are a poor measure of framework popularity because the architecture of the framework and the typical distribution channels can skew the number of npm pulls in a way unrelated to the number of projects utilizing it.

These numbers track actual, daily usage in production environments. You can't explain these numbers away, not if they're both competing in the same field. Both are distributed in the same way (npm, unpkg, various cdns), both websites show you how, both do not need build tools to function, both are better off with build tools. It would be pretty disingenuous to claim suddenly the only actual numbers we have are skewed.

I don't understand the link. We don't get Vue from NPM. I assume others don't either. That implies to me that the numbers implied in that chart are inaccurate at best.

Why do you say the statistics are inaccurate. They show a clear picture, actually the clearest we have, because if it weren't for actual usage stats we would have to rely on github stars, google trends and hear-say. Both react and vue release through the same channels, npm and cdns. Of course npm is the more important channel for modern environments and businesses. The point is that they both are subject to the same rules. The portion of users that like script tags use script tags with react as well. Those would fall out, but that happens on both fronts obviously.

The comment i made above, that most things going forward will happen in the react eco system, is supported by these statistics. If you have lots and lots of vue users that are still using script tags, and let us - without any data to confirm it - assume that there are less react users doing this, then that would speak volumes about the userbase at large, not the most forward leaning to say the least.

where do you get it?

No way! Vue is way better than react. Ok, it depends on personal opinion, but I think it’s s much nicer framework to work with.

Out of curiosity, what stage is your company at that your lawyer has an influence on your tech stack? Was this part of due diligence for fundraising?

Um, I work for a fortune 150 company. I'm not sure what stage that makes us, but we definitely don't do fundraising ;-)