News for hackers. Stuff that matters.
Re:Relicensing React, Jest, Flow, and Immutable.js by joshmanders on Friday September 22, 2017 @06:37PM (#15316522)
> everything from the Apache foundation to Wordpress.

Those were the only two.

Re:Relicensing React, Jest, Flow, and Immutable.js by CydeWeys on Friday September 22, 2017 @07:15PM (#15316792)
WordPress accounts for something like 19% of all websites, more so than any other single platform. Do not underestimate the importance of their decision.
Re:Relicensing React, Jest, Flow, and Immutable.js by KGIII on Friday September 22, 2017 @07:56PM (#15317041)
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...

Re:Relicensing React, Jest, Flow, and Immutable.js by irrational on Friday September 22, 2017 @08:13PM (#15317154)
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.
Re:Relicensing React, Jest, Flow, and Immutable.js by joshmanders on Friday September 22, 2017 @08:27PM (#15317234)
I too work for a Fortune 150 company and we've gone all in on React.
Re:Relicensing React, Jest, Flow, and Immutable.js by malloryerik on Friday September 22, 2017 @09:41PM (#15317529)
I'm told that one reason companies might have chosen to avoid React was that they could have imagined themselves be in competition with Facebook at some point, and thereby in the danger zone with their old BSD licence.
Re:Relicensing React, Jest, Flow, and Immutable.js by chrisco255 on Saturday September 23, 2017 @02:03AM (#15318400)
They explicitly said in their FAQ that you could use React even in direct competition. None of this matters now, of course, because it's been relicensed. The only impact the patents license ever had on anyone was iff they initiated a patent lawsuit against Facebook.
Re:Relicensing React, Jest, Flow, and Immutable.js by theptip on Saturday September 23, 2017 @04:59AM (#15318891)
The point is that if you're in direct competition, the chances of Facebook violating one of your patents is much higher, and then your cost of suing them is significantly increased (since you also have to rewrite your app).

If you're ok with trusting a direct competitor not to misbehave, then sure, use React under those terms while competing with FB. But large companies consider their patent portfolio to be a significant strategic asset, so it shouldn't be surprising that their legal counsel advises against accepting such a clause.

Re:Relicensing React, Jest, Flow, and Immutable.js by LiquidFlux on Saturday September 23, 2017 @03:08AM (#15318582)
Would the previous license have become relevant if Facebook initiated a patent lawsuit against you?

Even being on the back-foot when having to defend your patents, by refactoring React out of your application, was apparently damning enough for people to migrate.

Re:Relicensing React, Jest, Flow, and Immutable.js by irrational on Saturday September 23, 2017 @01:04AM (#15318229)
Yeah, obviously not all lawyers see eye to eye.
Re:Relicensing React, Jest, Flow, and Immutable.js by geerlingguy on Friday September 22, 2017 @08:11PM (#15317140)
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.
Re:Relicensing React, Jest, Flow, and Immutable.js by pknopf on Friday September 22, 2017 @06:41PM (#15316556)
We get it, React would have been fine with out them.

But it did matter.

It set a strong precedent.