Looks like React Native isn't included in the list for a license update.
The author of this Facebook Engineering post confirmed that React Native's license currently is the same as it's always been: https://twitter.com/dmwlff/status/911348886882607104 . I don't want to get into a big discussion about precise details here but pragmatically both the MIT and Facebook BSD+Patents licenses work well for most businesses, in particular those that aren't seeking to claim patent infringement again…
Relicensing React, Jest, Flow, and Immutable.js
201–210 of 528 posts
Re: Relicensing React, Jest, Flow, and Immutable.js
#202Earlier quoted context omitted.
I doubt it was related. The wheels to get this in motion must have started months in advanced, probably around the time ASF started advising against this license (labeling at as Category-X [1]) [1] https://www.apache.org/legal/resolved.html#category-x
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. G…
You're welcome everybody! And thanks for the assist, Wordpress!
Re: Relicensing React, Jest, Flow, and Immutable.js
#203Well, everyone that didn't want to use react, didn't use it because of the license, so I guess now these people will be happy too. Good news.
Re: Relicensing React, Jest, Flow, and Immutable.js
#204That 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.
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.
Re: Relicensing React, Jest, Flow, and Immutable.js
#205Can someone explain why this is good news? As I understood it, the former license was as permissive but additionally to that included a patent grant?
It's a response to placate folks who pick a stance based on the memes that the newstides wash up. In other words, it's not exactly good news at all, it's just a really big deal.
Re: Relicensing React, Jest, Flow, and Immutable.js
#206Earlier quoted context omitted.
> everything from the Apache foundation to Wordpress. Those were the only two.
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
#207Long live vue's chance at market domination!
Re: Relicensing React, Jest, Flow, and Immutable.js
#208Why not just go with BSD and drop the problematic patent clauses?
Re: Relicensing React, Jest, Flow, and Immutable.js
#209Earlier quoted context omitted.
Well...now back to writing code and shipping things...we can all put our irrational fantasies of patent litigation and being "unacquirable" startups due to React to rest.
I love HN, and I hate to risk my account, but I'm tired of responses like this. You're being an asswipe. There is no reason for you to respond this way. The lens upon which you view the world must be pretty god damned shallow to make these kinds of statements. If you want to be a fuckstick and reply like this, please find another community.