[lelandbatey]

In a statement from Facebook on August 18th, 33 days ago[0]:

    We have considered possible changes carefully, but we won't be changing our
    default license or React's license at this time. We recognize that we may lose
    some React community members because of this decision. We are sorry for that,
    but we need to balance our desire to participate in open source with our desire
    to protect ourselves from costly litigation.

Given that they apparently didn't think it was a big enough deal then, and what changed was Wordpress, I don't think it's incorrect to give them some credit.

[0] - https://code.facebook.com/posts/112130496157735/explaining-r...

[rdiddly]

Oh sure, a framework used on a quarter of the web might have had something to do with it, but actually it was my Hacker News comment the day after the Wordpress news, that put the final, decisive nail in the coffin. It captured so many people's hearts and minds, it ended up with seven upvotes ...and still counting. 1, 2, 3, 4, 5, 6, 7. Yup, 7.

You're welcome everybody! And thanks for the assist, Wordpress!

https://news.ycombinator.com/item?id=15254977

[chrisco255]

Hacker News does have an impact. Not any one person, but thanks to HN, things like this go viral in the tech community pretty fast.

[jhgg]

If I had to speculate, I'd suspect that even though they reaffirmed the BSD+Patent license publicly, FB probably started exploring the possibility of relicensing the projects shortly after that. Not to say WP saying they wont use react didn't help, but I don't think it was the "tipping" point for them at all.

Legal matters at big companies generally take months to resolve and come to consensus over. I can easily imagine their legal team evaluating all such scenarios that a change in license could hurt them (as they should), and that kind of research isn't something done in haste.

[tacon]

>Legal matters at big companies generally take months to resolve and come to consensus over.

Sure, at your typical big public company. But Facebook voting control is firmly in the hands of Mark Zuckerberg, and he doesn't have to wait for approval of a board of directors. Just like when he decided to buy Instagram for $1 billion in a matter of days. If Mark detected developer sentiment shifting, he can move just as fast as he wants to stanch the bleeding.

[abiox]

> If Mark detected developer sentiment shifting, he can move just as fast as he wants to stanch the bleeding.

how is react's popularity at all material to facebook's interests? at best it means you get more outside contributions, but you already have plenty of talent internally.

[djur]

Having popular, high-profile open source projects helps Facebook attract more and better talent in three primary ways:

First, it increases the likelihood that the average programmer already is familiar with the tools they'd use at Facebook. It's useful for them to be able to hire people who already know React, Reason, etc. On occasion, they'll manage to find highly talented developers who either contribute to their projects or build useful related projects, and then they can make those people an offer. Even better, sometimes that's an entire startup they can acquihire.

Second, it increases the prestige of a job at Facebook. Most of the core public functionality of Facebook isn't particularly interesting to me, for example, but the stuff they're doing with OCaml is. The chance of me working there is still essentially nil but it's definitely less nil than it would be if I didn't know about projects like that.

Third, it gives them something really valuable to offer skilled devs -- the ability to become widely known and respected for your contributions to a popular open source project. That's worth a great deal to some people.

[cookiecaper]

Software companies are all about lock-in, controlling the platform, making sure they have control of as much user and dev attention as possible. At Facebook's world-eater size, the better question is "Why should we not seek to dominate this element of the development platform?"

I can't pretend to know the exact rationale behind Facebook's decision to open-source React, but there are several things to gain from controlling a major piece of the web infrastructure: influence/clout with browser vendors (decisions that may negatively impact React's performance now threaten a huge percentage of the web, not just Facebook.com), the ability to introduce more and more Facebook-controlled technology with something like React as a shoehorn ("You liked React, try Flow..."), PR benefit/good vibes, and so forth.

Platform control is the real showdown among big software companies. It makes your company downright inextricable. Just ask Microsoft.

[rhizome]

If I had to speculate, I'd suspect that even though they reaffirmed the BSD+Patent license publicly, FB probably started exploring the possibility of relicensing the projects shortly after that.

If I had to speculate, I'd say they did a ton of research on existing licenses on the route to BSD+Patent, and they already knew what the best alternative would be if it came to that.