[blaqkangel]

That was incredibly unexpected. Facebook may very well end up in the majority's good graces with this move. I wonder how some of the bigger players will react (no pun intended) after their abandonment of React in lieu of Vue or some other framework. Interesting times indeed.

[MikeHolman]

>Facebook may very well end up in the majority's good graces with this move.

Really? They are doing the minimum possible to prevent an exodus from their stack after a public outcry.

[matthewmacleod]

There was no sign of an exodus. That’s ludicrously hyperbolic.

[CydeWeys]

Not at all. There was an exodus brewing. For starters:

https://ma.tt/2017/09/on-react-and-wordpress/

https://hacks.hyperspacer.com/app/items/15256532

[ng12]

An HN thread with a dozen responses? Hardly an exodus.

[davidgerard]

A quarter of all websites? An exodus.

[Rapzid]

Those websites weren't leaving, they never arrived..

[ng12]

Does the decision to use React or not affect end users? Each WordPress site is not making an independent determination.

[dankohn1]

CNCF had begun the process of moving two internal projects (that will be open sourced when they hit beta) from React to Vue.js. We'll now re-evaluate.

FWIW, why we prefer Apache 2.0: https://www.cncf.io/blog/2017/02/01/cncf-recommends-aslv2/

[_eht]

You must have missed a lot of news. A personal example: in my company we were comparing React vs Vue internally and the hint of licensing issues committed us to Vue.

This Facebook post gives us hope for GraphQL moving away from BSD+, as it is currently in our stack, but without doubt we are considering a move away due to uncertainty.

[irrational]

The same thing happened at my company (Fortune 150 company). We settled on Vue too, and it has been amazing. But if this had happened back when we were considering things we probably would have gone with React.

[octalmage]

Same here, this conversation is happening right now since we've built a pretty large application using React. I would much prefer to use React so this couldn't be better timing.

[tresil]

>In the wake of uncertainty about our license, we know that many teams went through the process of selecting an alternative library to React.

Evidently FB saw enough people leaving to prompt this change. No doubt they were also afraid of an exodus of their internal developers on these projects. High-profile developers will move on to companies where they know they'll have greater impact if that's seen to be at risk.

[Twirrim]

That's a strange claim given how many major projects have appeared on the front page of HN because of it, everything from the Apache foundation to Wordpress.

[joshmanders]

> everything from the Apache foundation to Wordpress.

Those were the only two.

[CydeWeys]

WordPress accounts for something like 19% of all websites, more so than any other single platform. Do not underestimate the importance of their decision.

[KGIII]

A bit higher, according to those who monitor these sorts of things.

Some 28.7% of sites use Wordpress.* Curiously, I've seen the 19% number being cited as 19% of all new websites use Wordpress. I'm not sure how 19% becomes 28.7%, but it may just be that sites using WP stick around longer.

* https://w3techs.com/technologies/details/cm-wordpress/all/al...

[irrational]

Only 2 that you know of. I work for a Fortune 150 company and we settled on Vue almost solely due to the licensing issue.

[joshmanders]

I too work for a Fortune 150 company and we've gone all in on React.

[geerlingguy]

Drupal was also close to picking a new library to replace or supplement Backbone, and React was just dropped out of the running (with a strong favor for Vue) a week or two ago.

[pknopf]

We get it, React would have been fine with out them.

But it did matter.

It set a strong precedent.

[hellofunk]

Huh? Where have you been for the last month or two?

[pier25]

React is pretty popular already. FB only really needs to change the license to keep the growth.

[pknopf]

Exactly.

React would have been fine, but to say the big players jumping ship didn't matter is just wrong.

[CorySimmons]

This. FB is intentionally leaving a ton of their ecosystem with the PATENTS virus.

Theorizing, but I suspect FB will begin targeting and picking off IP of apps built entirely on React stacks in a few years.

Please don't go back to them. Just contribute to Vue's ecosystem like crazy. Worst case scenario it'll keep FB in check.

[peterhunt]

When has this ever happened?

[ojr]

there was no exodus, React is the number one javascript framework in the job market in Boston and probably other tech hubs too

[irrational]

Yeah, we've already settled on Vue (because our lawyers forbade us from using React), but now I'm sure they would approve React. So... do we abandon our work on Vue (which so far is amazing) to switch to React since the React ecosystem is so large, or do we stay the course? Sigh. I wish Facebook had made this change a year ago.

[LibertyBeta]

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.

[swyx]

"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..

[epicide]

> 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.

[nathan_f77]

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.

[allover]

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.

[bpicolo]

> over a year of headaches and frustration

Seems like an argument against the react ecosystem

[erikpukinskis]

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".

[nathan_f77]

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.

[rhapsodic]

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.)

[nathan_f77]

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.

[rhapsodic]

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

[mlsarecmg]

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...

[philipodonnell]

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.

[mlsarecmg]

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.

[irrational]

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.

[mlsarecmg]

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.

[optimuspaul]

where do you get it?

[newsmania]

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.

[kimar]

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?

[irrational]

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

[AnkhMorporkian]

I... well, I kinda expected it. Facebook wanted their products to be used, but it was obviously their legal department that made them put the patent clause in. The more people who develop using their libraries, the more contributions they get back, and the more benefit they get from it.

I almost guarantee you none of the devs wanted that weird-ass patent clause in there, but I'm guessing that none of them thought that it was a big deal in the long run, just CYA shit you'd expect from a legal department.

They were proven wrong, and it impacted their market share, they raised a stink about it and they got it changed.

[dentemple]

>I wonder how some of the bigger players will react (no pun intended) after their abandonment of React in lieu of Vue or some other framework

Competing frameworks will now need a new "Reason #1 to use us instead" for their pitch-decks.

[tomascot]

As I see it this shows that you can't trust Facebook. And that Mark still is the same dude that once said "They trust me. Dumb fucks".

[flamedoge]

perhaps making a big deal out of it on mainstream media made it less unexpected? Odds are, it was a data-driven (shift in hype/marketshare) decision.

[nebabyte]

> I wonder how some of the bigger players will react (no pun intended) after their abandonment of React in lieu of Vue or some other framework

What do you expect them to do, shrug and come back? I doubt anyone who left based on concerns with their stack being owned by Facebook is likely to regret weaning themselves off of it.

[nilliams]

The react ecosystem is massive, and includes impressive projects like the various backends/renderers: react-native, react-sketch.app, react-vr, react-pdf, ink, that have no equivalent in other frameworks (or at least to nowhere near the same level of maturity), so yeah people ditching it may well regret it.