to be fair, Facebook could still sue anyone for any reason they can think of irregardless of what you&#x27;re using! ;-)

It’s asymmetrical in the sense that your license terminates even if you sue them for something that’s not in the software you’re using. I.e. they rip off your feature, and you’re using React, you’re f##d.

Was it asymmetrical? I thought it was a &quot;we won&#x27;t sue you for anything in this software, unless you sue us first&quot;. This change still allows them to sue you for any reason.

Death to asymmetrical patent clauses! Huge victory for OSS.

Wow, that&#x27;s a fantastic move, huge win for open source.

The problem is that there actually are patents covering GraphQL. So anybody who writes an alternative GraphQL server implementation is potentially infringing upon those patents.The issue with the GraphQL spec is that people actually want a patent grant for alternative implementations, but there isn&#x27;t one.

Is the GraphQL spec itself under the BSD+patents clause? Or just their specific implementation? Couldn’t somebody like the Apollo crew create their own implementation if necessary?

Waiting for update here <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;graphql&#x2F;issues&#x2F;351" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;graphql&#x2F;issues&#x2F;351</a>

&quot;This shift naturally raises questions about the rest of Facebook&#x27;s open source projects. Many of our popular projects will keep the BSD + Patents license for now.&quot;

Still an issue: <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;graphql&#x2F;issues&#x2F;351" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;graphql&#x2F;issues&#x2F;351</a>,There&#x27;s a patent: <a href="https:&#x2F;&#x2F;www.google.com&#x2F;patents&#x2F;US9646028" rel="nofollow">https:&#x2F;&#x2F;www.google.com&#x2F;patents&#x2F;US9646028</a>,and a recent discussion: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15289676" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15289676</a>

My guess is they go with Apache v2 for GraphQL.

My less cynical view (hope) maybe react-native isn&#x27;t due for an update soon and they&#x27;ll do it next time there&#x27;s a version bump?

See the fourth paragraph.&gt; This shift naturally raises questions about the rest of Facebook&#x27;s open source projects. Many of our popular projects will keep the BSD + Patents license for now. We&#x27;re evaluating those projects&#x27; licenses too, but each project is different and alternative licensing options will depend on a variety of factors.

That&#x27;s what gets me. There&#x27;s a very narrow list of packages that they&#x27;ve selected for the MIT treatment. Why isn&#x27;t the blog post something along the lines of &quot;We&#x27;re re-licensing all of our open source libraries under the MIT License and removing their patent clauses&quot;? It seems like they&#x27;re still trying to play games, and are only buckling to the pressure for a tiny number of libraries.

I may not intend to go suing FB for patent infringement, but if they infringe on one of my patents, or if they sue me for patent infringement, it&#x27;s really my only recourse.

Unfortunately lawyers don&#x27;t care about pragmatics :-(

The author of this Facebook Engineering post confirmed that React Native&#x27;s license currently is the same as it&#x27;s always been: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;dmwlff&#x2F;status&#x2F;911348886882607104" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;dmwlff&#x2F;status&#x2F;911348886882607104</a>. I don&#x27;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&#x27;t seeking to claim patent infringement against others.

Yeah, that is a downer. I&#x27;m going to wait and see what they decide to do about React Native before asking my company&#x27;s lawyers if we can use React now.

Looks like React Native isn&#x27;t included in the list for a license update.

Which parts do you rely on that haven’t changed it?

Except not all the pieces of the React ecosystem are changing license, so... we&#x27;ll probably end up staying with Vue.

Well, everyone that didn&#x27;t want to use react, didn&#x27;t use it because of the license, so I guess now these people will be happy too. Good news.

I guess you haven&#x27;t seen the Facebook projects where the patent grant was dumped after a handfull of people asked nicely. There it was more of a &quot;Yeah sure, why not?&quot; by the maintainer without much input from the legal team as it seems.

&gt; Why it took so long for the license change is a bit of a mysteryHave you ever worked at a large company with its own legal team? It&#x27;s not such a large mystery.

I suspect it also took time for the mounting discontent and for the number of voices to reach some kind of tipping point which then caused Facebook to begin the internal process of re-evaluating their licensing.Either way, it&#x27;s a good move.

&gt; Why it took so long for the license change is a bit of a mysteryBig organizations require more time and people to reach consensus at different hierarchical levels. Probably the legal department was the bottleneck.

Because their licence gave Facebook the upper hand if they wanted to come after you.MIT is like a standard when it comes to OS. At big companies, complicated licencies are very hard to get approval of.

&gt; a win for the open source community as a wholeI&#x27;m not sure how changing course from a direction that could have neutralized patents, to one engineered so patent aggressors aren&#x27;t hurt, is something that can be considered a win for the open source community.

This is a win for fans of the mentioned packages.  This license lives on in other facebook packages.

The article straight up says these repos are moving to MIT

&gt; Why it took so long for the license change is a bit of a mysteryBe careful. Facebook hasn’t said they’re removing the patents override completely. All they’ve said here is they’re changing their licensing, not what they’ll do. They may end up with BSD+Different patents grant. Make sure you check the changes next week. I doubt it will be straight BSD or they would have said it.

This is a very smart move by Facebook, and a win for the open source community as a whole. Why it took so long for the license change is a bit of a mystery, but removing the complications of software patents from their licenses will help further drive adoption and remove the precedent they were in danger of setting.

There was a graphql Patent grant issue as well.

This is all so complicated, and there&#x27;s so much conjecture and uncertainty from the community. Engineers interpreting legalese is a bad idea. We need impartial lawyers to explain each of these licenses in plain English, including the ramifications and side effects to consider, and put the debate to rest.This has all been so tiring.

Yup. There’s going to a lot of self congratulation going on in the comments but basically all this has done is remove explicit granting of patents.Like... ok, great, better really hope you never get into legal issues with FB now

MIT license doesn&#x27;t contain any patent clause. So it is the same as BSD + Patents with patents part revoked. Thus, in theory, FB can still have a case on patent over React even if you use the source with copyright grant.Apache 2.0 has a patent grant from my understanding.

Apache 2.0 has a patent clause going in the opposite direction of what they were originally trying to do. That&#x27;s probably why they didn&#x27;t use it.For what it&#x27;s worth, the software that I&#x27;m developing at a Big 4 is released under the Apache 2.0 license.

Why pick a license with much more legalese? MIT is pure OSS love, no BS no need to hire a legal team. You just use it. I love the MIT license.Why would you have preferred the Apache 2.0 license?

Why not Apache 2.0 though? That would have been a logical choice.

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&#x2F;marketshare) decision.

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

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

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&#x27;t go back to them. Just contribute to Vue&#x27;s ecosystem like crazy. Worst case scenario it&#x27;ll keep FB in check.

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

&gt;Facebook may very well end up in the majority&#x27;s good graces with this move.Really? They are doing the minimum possible to prevent an exodus from their stack after a public outcry.

&gt;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 frameworkCompeting frameworks will now need a new &quot;Reason #1 to use us instead&quot; for their pitch-decks.

I would stay with Vue. While the react world is bugger it&#x27;s mostly made up of competing solutions instead of distinct tasks.That said, this healthy Vue&#x2F;Angular&#x2F;React competition has been great for us devs.

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&#x27;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: <a href="http:&#x2F;&#x2F;www.npmtrends.com&#x2F;angular-vs-react-vs-vue-vs-@angular&#x2F;core" rel="nofollow">http:&#x2F;&#x2F;www.npmtrends.com&#x2F;angular-vs-react-vs-vue-vs-@angular...</a>

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?

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.

Yeah, we&#x27;ve already settled on Vue (because our lawyers forbade us from using React), but now I&#x27;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.

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&#x27;m guessing that none of them thought that it was a big deal in the long run, just CYA shit you&#x27;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.

The react ecosystem is massive, and includes impressive projects like the various backends&#x2F;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.

&gt; 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 frameworkWhat 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.

As I see it this shows that you can&#x27;t trust Facebook. And that Mark still is the same dude that once said &quot;They trust me. Dumb fucks&quot;.

That was incredibly unexpected. Facebook may very well end up in the majority&#x27;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.

Good move by Facebook. This is highly appreciated.

But would using those libraries infringe upon any patent of TheFacebook?

React Native would be a notable omission, unless it&#x27;s included as part of React.

Kudos to Facebook and the React community for prompting this change, this was the right move.

At least it might give the louder parts of the community that have been consistently complaining about this issue a good reason to stop shouting quite as much

Because an unspecified parent grant is most likely an implied patent grant, and especially for FOSS there is a very strong case since your are explicitly permitted to study, modify, and use any part of the code.

Yeah, exactly, what does this actually accomplish besides putting the user in a worse situation where they are no longer given any sort of patent grant?

&gt; Probably because they have no patents that cover the concepts these libraries introduce.Apache 2.0 certainly doesn&#x27;t require you to have patents in order to use it (&quot;applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s)&quot;)

They have the patent: <a href="https:&#x2F;&#x2F;www.google.com&#x2F;patents&#x2F;US20170221242" rel="nofollow">https:&#x2F;&#x2F;www.google.com&#x2F;patents&#x2F;US20170221242</a>. Just MIT is a good option, I don&#x27;t really understand why they don&#x27;t want to &quot;fix&quot; the patent grant to be like Apache 2.0 or Google&#x27;s. Why relicense everything when fixing 1 sentence would fix the problem completely.

Probably because they have no patents that cover the concepts these libraries introduce. Perhaps wit some of the others they will go Apache v2. People have been so worked up by the FUD that Facebook can&#x27;t even relicense under MIT one of the de facto open source licenses without being met with suspicion.

To quote a comment in a similar thread, apparently there&#x27;s such a thing as an implied patent license:Implied patent licenses:<a href="https:&#x2F;&#x2F;www.wilmerhale.com&#x2F;pages&#x2F;publicationsandnewsdetail.a.." rel="nofollow">https:&#x2F;&#x2F;www.wilmerhale.com&#x2F;pages&#x2F;publicationsandnewsdetail.a...</a>.<a href="https:&#x2F;&#x2F;copyleft.org&#x2F;guide&#x2F;comprehensive-gpl-guidech7.html" rel="nofollow">https:&#x2F;&#x2F;copyleft.org&#x2F;guide&#x2F;comprehensive-gpl-guidech7.html</a>Basically, if you sell or license a product that requires a patent to work, courts have generally held that you grant an implied patent license for any patents that the product might require. If you explicitly reference patents within the license, however, then whatever terms you explicitly write into the license supersede this implied patent license. BSD+patents (and Apache 2) have explicit patent language; paradoxically, this makes them more restrictive than licenses like MIT, BSD, or GPL that don&#x27;t mention patents at all.

Wait, so they&#x27;re replacing a license that has a dodgy patent grant that everyone distrusted, with a license that doesn&#x27;t have a patent grant at all? Why not Apache?

Well...now back to writing code and shipping things...we can all put our irrational fantasies of patent litigation and being &quot;unacquirable&quot; startups due to React to rest.

Seriously, big thanks go out to Wordpress.  They&#x27;re no small part of this win for Free Software.

They had doubled down on their licensing decision on Aug 18th specifically citing Apache: <a href="https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-react-s-license&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-r...</a>This is very clearly a response to WordPress. Nicely played Matt.

It was only a month ago that Facebook re-confirmed its commitment to its patent license: <a href="https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-react-s-license&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-r...</a> <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15050841" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15050841</a>

In a statement from Facebook on August 18th, 33 days ago[0]:<pre><code> We have considered possible changes carefully, but we won&#x27;t be changing our
 default license or React&#x27;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.
</code></pre>
Given that they apparently didn&#x27;t think it was a big enough deal then, and what changed was Wordpress, I don&#x27;t think it&#x27;s incorrect to give them some credit.[0] - <a href="https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-react-s-license&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-r...</a>

I disagree. I think it was entirely related. Facebook could likely put up with a few dissenters here and there, but a major defector such as Wordpress is a canary: they likely feared that this would be the first domino to topple React&#x27;s supremacy.FB: &quot;...we know that many teams went through the process of selecting an alternative library to React. We&#x27;re sorry for the churn. We don&#x27;t expect to win these teams back by making this change, but we do want to leave the door open.&quot;This can seem like a response to the community at large, but can also be read as a direct response to Wordpress&#x27; comments:WP: Automattic will also use whatever we choose for Gutenberg to rewrite Calypso — that will take a lot longer, and Automattic still has no issue with the patents clause, but the long-term consistency with core is worth more than a short-term hit to Automattic’s business from a rewrite. Core WordPress updates go out to over a quarter of all websites, having them all inherit the patents clause isn’t something I’m comfortable with.Now if someone (i.e. an Actual, Impartial Lawyer) can explain if changing to MIT actually changes anything.EDIT:As others have pointed out, FB reaffirmed its decision to maintain the patents clause on Aug 18th (33 days ago): We recognize that we may lose some React community members because of this decision. [1] But they change their minds 8 days after the Matt published the On React and Wordpress article.This pretty much proves that the decision to move to MIT was heavily influenced -- or perhaps in direct response to -- Wordpress&#x27; decision to ditch React.[1]<a href="https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-react-s-license&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-r...</a>

Shot callers; they exist. Lawyers don&#x27;t actually control these companies, they just have a wide berth.

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] <a href="https:&#x2F;&#x2F;www.apache.org&#x2F;legal&#x2F;resolved.html#category-x" rel="nofollow">https:&#x2F;&#x2F;www.apache.org&#x2F;legal&#x2F;resolved.html#category-x</a>

Agreed. Wordpress helped making it happen faster that&#x27;s for sure.

FTA:&gt; I think Facebook’s clause is actually clearer than many other approaches companies could take, and Facebook has been one of the better open source contributors out there. But we have a lot of problems to tackle, and convincing the world that Facebook’s patent clause is fine isn’t ours to take on. It’s their fight.My interpretation is that due to the negative publicity that Facebook has garnered with their license, they didn&#x27;t want to scare people away from using&#x2F;building on top of their platform by using their library even though they themselves did not have a problem with the license.It&#x27;s understandable how that might be the final straw for Facebook when even people who don&#x27;t have a problem with their license won&#x27;t use their libraries for that reason.

They feared that for example the Apache Foundation wouldn&#x27;t use WordPress, and so with others.And yes, the Patents part of that extends downstream to anything using it, that&#x27;s the dangerous part of patents. It applies to everything that does that — even in independent implementations.

4.  The license causes Fear, Uncertainty and Doubt for those considering our product.  We (WordPress) do better by not causing this FUD for our customers.

&gt; Does React&#x27;s BSD + Patents license extend downstream like that?Yes, why would it not?

I think the key point in that blog post is this:&quot;Core WordPress updates go out to over a quarter of all websites, having them all inherit the patents clause isn’t something I’m comfortable with.&quot;It&#x27;s one thing to look at the license and guess that it&#x27;s vanishingly unlikely you&#x27;ll ever be in an intellectual property fight with FB (and it sounds like the counsel Automattic consulted with came to that conclusion for Automattic).It&#x27;s another thing to make that decision for everybody downstream using software that you distribute. Particularly when that&#x27;s a reaaaally large number of people.I&#x27;m on much less solid ground in speculating about more, but it&#x27;s often interesting to watch the contents of speech when people are working to assure you of something:&quot;One nice thing about this apartment is that it&#x27;s very secure.&quot; (That&#x27;s interesting. Why is it important that this apartment is very secure? Is the neighborhood not so much secure?)&quot;This guy we&#x27;re interviewing here is not being interviewed for your position.&quot; (That&#x27;s interesting. Why do I need to know that, manager?)In the case of this post, between the lines I potentially see something like:&quot;Hey FB, we don&#x27;t feel threatened by the license, and you know, he who writes to code makes the rules, like Linus says. You&#x27;re obviously doing what&#x27;s right for you, from your point of view, and we&#x27;re sure you know what&#x27;s best for you, and if you&#x27;re doing right by yourself, do you need to even ask if you&#x27;re doing the right thing?You do you, bro. And we&#x27;re sure you won&#x27;t be mad that we wanna let everybody else be themselves, too.&quot;Not sure it&#x27;s there, I could be reading more into it than I need to.

Sorry, I&#x27;m confused, can you help me understand that blog post? I&#x27;m getting three messages from it:1. We like React a lot with or without the license.2. It&#x27;s not our job to convince the world React&#x27;s patent license is fine.3. We&#x27;re substantially moving away from React, including large rewrites....why are they moving away from React? I&#x27;m confused, do they believe using React implicitly supports it? They&#x27;re already vocally supporting it.I don&#x27;t have an opinion or a dog in the race with regards to the React and patent license drama, but I legitimately don&#x27;t understand why this blog post (or the underlying decisions) was written. In my opinion it feels like a huge deal to decide to rewrite a piece of production software, especially if you like the software already. So what am I missing?Are they concerned that people won&#x27;t use WordPress because it has React components? Does React&#x27;s BSD + Patents license extend downstream like that?EDIT: Thank you for downvoting me twice for asking an honest question folks...

But they are building a real-time app![1] The new Gutenberg editor is going to be much more dynamic than the old editor.<a href="https:&#x2F;&#x2F;wptavern.com&#x2F;wordpress-new-gutenberg-editor-now-available-as-a-plugin-for-testing" rel="nofollow">https:&#x2F;&#x2F;wptavern.com&#x2F;wordpress-new-gutenberg-editor-now-avai...</a>

Wordpress has a pretty good JSON api that you can use with crud operations: <a href="https:&#x2F;&#x2F;wordpress.org&#x2F;plugins&#x2F;rest-api&#x2F;" rel="nofollow">https:&#x2F;&#x2F;wordpress.org&#x2F;plugins&#x2F;rest-api&#x2F;</a>There&#x27;s also already a theme that uses React: <a href="https:&#x2F;&#x2F;themes.redradar.net&#x2F;foxhound&#x2F;" rel="nofollow">https:&#x2F;&#x2F;themes.redradar.net&#x2F;foxhound&#x2F;</a>With those two things you could build a pretty good web app. The only thing is you&#x27;d be in WordPress land and isn&#x27;t glamorous.

Yes, that React is really convenient for building practically any type of web app, not just real-time apps, and they probably want the slick and seamless user experience they can get by building a progressive web app in React.

React has the largest front end ecosystem short of JQuery. And it&#x27;s a great declarative way of describing UI.

Though I am a bit curious about why WordPress would need React in the first place. It&#x27;s not like they&#x27;re building a real-time app. Am I missing something here?

So, Facebook knuckled under to increasingly intense public and commercial pressure.In this instance.I don&#x27;t think they should be particularly rewarded for this. I think we should keep in mind what it took to get to this point.And that, absent such pressure, individual organizations and people, and perhaps our collective society, remain at their... &quot;mercy?&quot;Remain under their thumb. Whether that thumb presses down this year. Or next. Or... we just don&#x27;t know.In other words, I&#x27;d remain cautious about whether and how far I move under their umbrella -- tech-wise, or other.

Thank them for what? I don&#x27;t get it. It sounds to me that they just ran away from the problem. The problem in my eyes being software patents not the BSD+Patents license.  But sure, thanks for being weenies.

Thank you, Wordpress.[1][1] <a href="https:&#x2F;&#x2F;ma.tt&#x2F;2017&#x2F;09&#x2F;on-react-and-wordpress&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ma.tt&#x2F;2017&#x2F;09&#x2F;on-react-and-wordpress&#x2F;</a>

So, sucks to be WordPress or are they coming back now?

Nice. Now if only Facebook changed their attitude regarding tracking and profiling of users, letting users be the &quot;product&quot;, grabbing the attention of users with psychological tricks and fake news, then perhaps I&#x27;d consider using and supporting their open source projects.

&quot;I&#x27;m sorry you&#x27;re mad&quot;

For all the shit facebook got before, this is a pretty surprising move. I don&#x27;t think anyone could have predicted this.

People were unhappy with the terms of the patent grant: it stated that FB would grant you a license to its related patents, BUT, if you were to sue FB for patent infringement, your license to use the covered software is terminated.But I very much agree and am puzzled why everyone seems to think this latest move is such a great thing. Removing the patent grant entirely isn&#x27;t so great.

That&#x27;s not fair. The lawyers at my company (Fortune 150) may have been irrational in forbidding us from using React, but they were hardly influenced by memes.

It&#x27;s a response to placate folks who pick a stance based on the memes that the newstides wash up.  In other words, it&#x27;s not exactly good news at all, it&#x27;s just a really big deal.

Can 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?

I&#x27;m just glad we can put this one to bed, and focus our efforts on finding the next silly reason not to use React.

Yeah, that&#x27;s why all the upheaval against the patents grant was so fucking stupid.

The way I interpret it is, explicit patent license implies _less_:- Explicit patent license specifies why &#x2F; how it can be revoked.- Without an explicit patent license, patent infringement case (by Facebook) against a party that uses Facebook&#x27;s OSS would be become harder, because one may argue that such grant is implied by Facebook open sourcing the software.

That&#x27;s what all the Facebook &amp; React folks were arguing. Facebook doesn&#x27;t want to do unconditional patent grants. Plus, they decided that the weak patent retaliation clause in Apache 2 license wasn&#x27;t strong enough. This new license is strictly riskier for people than the old license, but it&#x27;s more familiar, so people won&#x27;t freak out.

GPL 3 adds an anti-patent-treachery clause not unlike the Apache 2 clause.React Patent Grant Version 2: <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react&#x2F;blob&#x2F;b8ba8c83f318b84e42933f6928f231dc0918f864&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react&#x2F;blob&#x2F;b8ba8c83f318b84e42933...</a>The license granted hereunder will terminate, automatically and without notice,
if you (or any of your subsidiaries, corporate affiliates or agents) initiate
directly or indirectly, or take a direct financial interest in, any Patent
Assertion: (i) against Facebook or any of its subsidiaries or corporate
affiliates, (ii) against any party if such Patent Assertion arises in whole or
in part from any software, technology, product or service of Facebook or any of
its subsidiaries or corporate affiliates, or (iii) against any party relating
to the Software.Apache 2 Section 3: <a href="http:&#x2F;&#x2F;www.apache.org&#x2F;licenses&#x2F;LICENSE-2.0" rel="nofollow">http:&#x2F;&#x2F;www.apache.org&#x2F;licenses&#x2F;LICENSE-2.0</a>If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.GPL 3 Section 10 (See also Section 11): <a href="https:&#x2F;&#x2F;www.gnu.org&#x2F;licenses&#x2F;gpl-3.0.en.html" rel="nofollow">https:&#x2F;&#x2F;www.gnu.org&#x2F;licenses&#x2F;gpl-3.0.en.html</a>You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.Edited for spacing

Furthermore, suppose you&#x27;re some company like, say, IBM which figured out some way to say, safely double the energy density and recharge cycles of Lithium Ion batteries, which you have patented. Let&#x27;s also assume that you are shipping some critical problem which is dependent on React. Facebook could now freely use your patented idea, and violating it left, right, and center, and if you try to sue them for violating that patent, you&#x27;re completely f*cked.So Facebook&#x27;s idea works fine if you believe that Patents as a Thing are bad (all patents, not just software patents), and should not be asserted under any circumstances, and it&#x27;s fine for Facebook to arbitrarily violate any patent of any company who has become dependent on React.

This is highly confusing to me.If implicit patent grants are a thing, why have more modern licenses like Apache 2 and GPL 3 made it a point to include explicit patents grants in the language of the license?Wouldn’t their legal counsel advise them against it if it was redundant?

Has this implied patent license ever actually been tested in court wrt to open source software?

Implied patent licenses:<a href="https:&#x2F;&#x2F;www.wilmerhale.com&#x2F;pages&#x2F;publicationsandnewsdetail.aspx?NewsPubId=95535" rel="nofollow">https:&#x2F;&#x2F;www.wilmerhale.com&#x2F;pages&#x2F;publicationsandnewsdetail.a...</a><a href="https:&#x2F;&#x2F;copyleft.org&#x2F;guide&#x2F;comprehensive-gpl-guidech7.html" rel="nofollow">https:&#x2F;&#x2F;copyleft.org&#x2F;guide&#x2F;comprehensive-gpl-guidech7.html</a>Basically, if you sell or license a product that requires a patent to work, courts have generally held that you grant an implied patent license for any patents that the product might require. If you explicitly reference patents within the license, however, then whatever terms you explicitly write into the license supersede this implied patent license. BSD+patents (and Apache 2) have explicit patent language; paradoxically, this makes them more restrictive than licenses like MIT, BSD, or GPL that don&#x27;t mention patents at all.

If there is an implicit patent grant, we have more rights. I think there is a strong case that the implicit grant exists, and would vastly prefer seeing projects licensed under MIT than under the Facebook license.Apache 2.0 would have also been acceptable, as it had a better explicit patent grant. I&#x27;m actually a little surprised they didn&#x27;t choose it.

I&#x27;m not well versed enough in the various licenses to compare BSD+Patents and MIT, but in my opinion, this is more of a move to appease the community than anything dealing with the benefits&#x2F;disadvantages of the license being used.You may be right that this might actually reduce our rights, however, the MIT license is well known and accepted by many in the developer community. It&#x27;s been around long enough that developers know what they are agreeing to when they use something with an MIT license. With the BSD+Patents license, the biggest concern was not understanding what you were getting into when using React.Facebook recognized this and conceded despite still believing in the BSD+Patents license to be better. So in that sense, this makes a lot of sense as it:* alleviates community concerns* builds up their standing with developers* generates a lot of good PR* draws attention away from alternative solutions which were getting a lot of publicity from all of this (Vue.js, Marko, Preact, etc.)It would be nice though to have a lawyer chime in on the differences between BSD+Patents and MIT.

From my layman perspective, jQuery has MIT license, now React has MIT license. jQuery was once ubiquitous, now React can be too.I&#x27;m likely oversimplifying, but that&#x27;s about as much as I understand on licenses

There hasn&#x27;t been a single patent covering a standard React implementation found yet. Someone found one that might cover a niche case, but the bottom line is no one really knows if any patents of any substance or having broad claims will actually ever issue.That combined with the implied licenses means there was a patent clause causing a ton of unecessary hand-wringing.The reality is every company of FB&#x27;s size is patenting every developer&#x27;s latest dump if it can get through the patent office.

Wait, this doesn’t solve anything. They replaced BSD with MIT, which are basically the same license and then they removed any explicit patent grant. So this means the user is actually granted less rights then before.Am I missing something or does this make zero sense?

Props to Facebook! A wise move given recent community sentiment against Facebook OSS. I will be glad to continue using Facebook OSS software.

Yes, it is: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;MIT_License#Comparison_to_other_licenses" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;MIT_License#Comparison_to_othe...</a>

Is the MIT license considered to come with an implicit patent grant?

By that logic we&#x27;d never have any new licenses, because everyone would be afraid to use them. We take it on faith now that whenever a new release of the GPL comes out, we won&#x27;t be afraid of it just because it&#x27;s new. People had problems with GPLv3 when it came out, but those problems were about specific parts of the license, not &quot;oh god it&#x27;s new and scary and we don&#x27;t know how to interpret it&quot;. And that&#x27;s the GPL, a license orders of magnitude more complex than BSD+Patents.As an aside, I realized I read FB&#x27;s license wrong -- it actually is even better for users of it, and specifically says that the patent termination clause only goes into effect if the user is the aggressor. If FB comes after you for a patent claim, you can counter-sue all you want without losing your license. So FB is actually doing the absolutely correct thing here.

I think it&#x27;s more about the complexity of licensing, patents, and the uncertainty a new license presents.Using a license that&#x27;s been in use for a long time, and has the endorsement of major OSS organizations, is pretty much always more comfortable for developers.I wasn&#x27;t uncomfortable enough with their licenses to rule out their projects based on the license, but I understand the folks who were. Even if my reading of the license makes me unafraid of it, there was enough uncertainty about how a court, particularly courts that have a history of siding with patent trolls, might interpret the license, for it to make some people nervous.Also, the belief that the copyrights and patents involved will always belong to a benevolent actor ignores a lot of tech history. See: SCO, Oracle, etc. for examples of a previously decent stakeholder being consumed by a more malevolent and litigious one with a different interpretation of the law and the license. facebook may be a huge, unassailable, force today...can we be certain that in ten years that&#x27;ll still be true? I&#x27;d bet on it, but I also won&#x27;t be shocked if something dramatic happens. Sun looked pretty unassailable through the 80s and 90s, and then they didn&#x27;t.Big companies building big projects have to think about these things if they want to be responsible about the future of their projects. (Again, I agree that in this case, the fear is probably overblown. But, I get where it&#x27;s coming from.)

And at small to medium-sized businesses, they don&#x27;t have in-house IP attorneys and their in-house counsels (or outside lawyers on retainer) will likely punt such questions to an outside firm or IP specialist. And that will come with an unattractive price.

I don&#x27;t get your point about MIT licensed being a standard. The BSD license used by React is a standard too.

This is the first time I&#x27;ve seen &quot;put your head in the sand&quot; as an actual recommendation, instead of being characterized as something not to do.  And as far as recommendations go, it&#x27;s more than a little bit nutty.

So, in other words, what you&#x27;re effectively saying is that everyone&#x27;s reaction to this is irrational, but understandable. People understand the MIT license (or even just the regular BSD license), but as soon as something brings patents into the mix, even if the clause actually gives you more rights and legal cover, people get scared and don&#x27;t want to deal with it?That&#x27;s... sad.&gt; Being aware of patents ... makes punitive damages worse.Sure, but that doesn&#x27;t have anything to do with a BSD+Patents license. The license doesn&#x27;t say &quot;you also must do extensive patent research when using our software&quot;. You have to actually be aware of the patents that you&#x27;re infringing to be held liable for extra damages.

If it&#x27;s licensed MIT, the Engineers just say &quot;it&#x27;s MIT license like half of the libraries we already use&quot; and it&#x27;s a legal non-issue.If the license is not one of the standard ones already in use, and it mentions patents, suddenly legal gets involved and it&#x27;s a disaster. They&#x27;re very risk-adverse and no one&#x27;s really sure what will happen when it gets to court. It doesn&#x27;t have to make sense - after all, most software patents don&#x27;t make sense, and most software patent lawsuits don&#x27;t make sense.Copyright makes some sense - some entity wrote the code and has (or has not) given explicit permission for others to use it, and under common open-source licenses those terms are reasonably well understood. But patents can come out of left-field and be unrelated to the user or the producer of the code. Being aware of patents (which should not cover what you&#x27;re doing or should not exist) makes punitive damages worse. Again, best to just put your head in the sand and hope the patents don&#x27;t notice you. Any language about patents adds complications which no one wants to figure out.

I think you have it backwards. The facebook patent license puts all the power in their hands, and none in yours: they can still sue you for violating their patents, but you can&#x27;t sue them. It would be a much, much worse patent regime.

&gt;Unethical fevelopers that work at shitty companies with shitty lawyers were annoyed that they couldn&#x27;t use React. That&#x27;s all there is to it.Apache is an unethical foundation with shitty lawyers? I admire the goal of eradicating software patents, to me BSD+Patents was an unsuccessful way to do it. It hurt OSS projects more than it hurt private projects.

Unethical developers that work at shitty companies with shitty lawyers were annoyed that they couldn&#x27;t use React. That&#x27;s all there is to it.I loved BSD+patent as one of the few potentially successful attacks on the awful software patents regime that we currently live under. This defeat means we are probably stuck with it for the rest of our careers.

It seems like people never get tired of not reading the PATENTS file. “Wildly aggressive?” Please. The agreement explicitly forbids Facebook from revoking your patent grant if they are the aggressor. Without the agreement (i.e. just BSD) Facebook is free to sue you for patent infringement. They add a file that says they can’t do that unless you sue them first and suddenly people are out for blood. Salem 2.0.

But it wasn&#x27;t unpalatable at Google, MS, Apple and many other large companies.

No, they said your license didn&#x27;t terminate if you had a counterclaim against them. The only event that license terminated was if YOU attacked Facebook.

Yes, I get that, and addressed the power imbalance in my comment...But on second reading I realize I was wrong (in a good way). Facebook&#x27;s patent grant specifically says that if they sue you for patent infringement, and you counter-sue with something that is unrelated to the software of FB&#x27;s that you are using, then your license to use FB&#x27;s software is NOT terminated. That&#x27;s actually entirely reasonable and great.

It&#x27;s not just big companies necessarily either. Say you are a small startup working on something really innovative and you have a patent on part of your work. Facebook decides to build something similar, violating your patents in the process, and they are going to put you out of business. If one of your core technologies is react under the BSD + Patents license, then you are screwed. You can&#x27;t sue to save your business because even if you do you have to immediately recall all of your software and replace React.Sure, not everyone is in that situation. Facebook is big enough though that if you have any patents you have to be _very_ careful about that license.

Hasn&#x27;t that already happened?Oracle v. Google?

The current state of things is that patents are stockpiled as deterrents, kind of like nuclear weapons. All of the big companies know that if they sued one another over some patent claim, the other side would retaliate, and it would be a big mess with no real winners.Facebook&#x27;s patent clause disarms all their opponents, but leaves them free to attack. It&#x27;s actually a wildly aggressive, offensive weapon, surprisingly - just like how nuclear missile defense is one of the more provocative technologies out there that possibly makes nuclear conflicts more probably.That&#x27;s why it&#x27;s totally unpalatable, at least at the big companies.

This. I don&#x27;t even want to know how many patents we&#x27;re all infringing on in everything we ship. We all just sort of sweep this under the rug. No one ever does a technical&#x2F;patent analysis. Is patent check part of your deployment pipeline? I highly doubt it. There&#x27;s probably tens of thousands of broadly worded software patents out in the wild. The only thing that keeps the industry safe is how difficult it actually is to do that analysis because of the inherent complexity in both software and patent law.

&quot;and the more you think about patents the more you wish you were a plumber and not a dev so all you&#x27;d have to deal with is toilets blocked with shit, and not software patents, which are much worse.&quot;This.

The sad thing is that Facebook&#x27;s policy was obviously informed by exactly this point of view, that, essentially, software should not be patented.It&#x27;s the backlash that was led by people who considered it a realistic possibility that they may, some day, want to sue Facebook for infringing on one of their precious patents.

I think the story is this:1. Software patents are a huge, huge, existential crisis facing our industry.2. So huge, in fact, that nobody wants to deal with it. We can&#x27;t realistically figure out if the libraries we are using are covered by patents, and given how broken issuance is, they probably are.3. So the only practical solution is to use MIT licensed libraries, pretend there&#x27;s no patent issue, and put our heads in the sand.4. But Facebook&#x27;s BSD+Patents license made us think about patents. Nobody stopped and said &quot;can we use Angular? Are there patents on core elements of it?&quot;. But people did stop and ask that about React, because Facebook was (accidentally) making people think about patents, and the more you think about patents the more you wish you were a plumber and not a dev so all you&#x27;d have to deal with is toilets blocked with shit, and not software patents, which are much worse.5. Now that it&#x27;s under an MIT license it&#x27;s just as dangerous to use React (maybe more) but we can pretend it&#x27;s safe again.Notice that Wordpress&#x27;s decision to switch from React (which probably led to this) was quite clear: They were not switching due to patent concerns about React, they were switching because the non-standard license was stirring up FUD and making people ask them uncomfortable questions. (We know this because they explicitly said so, and also because the leading contender for a new library was Preact, which is strictly more dangerous from a patent point of view than React under every possible circumstance, but has a license that lets your pretend everything is okay easier.)

As summed up my Dan Abramov: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;dan_abramov&#x2F;status&#x2F;911397710791667712" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;dan_abramov&#x2F;status&#x2F;911397710791667712</a>&gt; With MIT nobody knows if you have those grants in the first place because there was never a court precedent. But not our hill to die on

The root problem is that it&#x27;s a revocable license. This arguably makes it not a free software license at all.

So... I guess I still don&#x27;t understand what was wrong with BSD+Patents.I get that there&#x27;s legal uncertainty: I can imagine some companies, especially larger ones, not wanting to give up their patent-suit option just because one random small team in their org is using React. And barriers to adoption aren&#x27;t a great idea when one of your goals is wide adoption.Overall, though, I think making it much harder to file patent suits -- at least for software patents -- is a great thing. Facebook&#x27;s (and others&#x27;) implementation of it might have left something to be desired, and they&#x27;re certainly a large company with a lot of resources behind them, so the power dynamic might be a bit lopsided, but...Well, let&#x27;s just say I&#x27;m a small company or individual who wants to release some open source code. Doing so under a BSD+Patents-style license gives me some protection from any big players who decide to use my software. How is this a bad thing?I suppose I hold a pretty strong anti-patents stance, though. I&#x27;d be happy if (most?) patent protection just went away entirely.As an aside, note that it looks like FB is going with straight MIT. So they&#x27;re not even giving users of their software a patent grant at all anymore[1], and reserve the right to sue you later just for using their software, if they happen to have a patent on something in it.[1] Yes, there are some legal opinions that the MIT license&#x27;s language includes an implicit patent grant, but I don&#x27;t believe that&#x27;s a settled matter.

It sucks that it took this long, but at the end of the day, they&#x27;ve done the right thing.

&gt; We&#x27;ll include the license updates with React 16&#x27;s release next week.Was this release date known before now? I can&#x27;t find it anywhere else on Google or Twitter. Man, talk about burying the lede.

Most of React&#x27;s competitors are licensed MIT I&#x27;m curious what you think folks should switch to.

&gt; Case closed. Could not have picked a better license, thank you Facebook.Case not closed, patents still pose a threat. They could (and arguably should) have picked better license, something with explicit permissive patent grant, such as Apache 2.0. This move can barely constitute even as lip service to appease the masses.

&gt;Next week, we are going to relicense our open source projects React, Jest, Flow, and Immutable.js under the MIT license.Case closed. Could not have picked a better license, thank you Facebook. MIT or bust, I try not to use any other types of licenses in products&#x2F;libraries I choose for work and personal use.

They should have done this a year ago - before my company settled on Vue.

I had a feeling they&#x27;d come round to this but not so quickly.

This can&#x27;t be upvoted enough. At this point people are just looking for excuses to hate React.

Vue: MIT
Angular: MIT
Preact: MIT
Knockout: MIT
JQuery: MIT
Backbone: MIT
Ember: MIT
Aurelia: MIT...React switches to MIT...People still FUD. WTF.

As you seem to consider the MIT license insufficient, you evidently don&#x27;t use any mainstream modern JS library. Tell me again why you think your opinion matters or contributes anything to the discussion?

Before all the congratulating goes too far, it is important to realize that only some projects had the license change but it went to an MIT license. What people really want is for these projects to be licensed under Apache 2 (like they did with RocksDB).The other thing is that there are many projects that are STILL going to be on the BSD+Patent license. These include widely used projects such as React Native and GraphQL.This behavior is reminiscent of their strategy of invading their users&#x27; privacy and then retracting a bit and then doing it again. Wash, rinse, repeat...

&gt; we still believe our BSD + Patents license provides some benefits to users of our projectsIs there somewhere where anyone has elaborated a case as to what those benefits to users would actually be?

The world won&#x27;t end for Facebook because it doesn&#x27;t have this clause.

Facebook almost ruined these awesome projects just because of some nut head not thinking through. Hopefully this will recover them on many fronts in opensource community. I don&#x27;t know if they were just playing with our emotions or something but I personally feel happy to hear the news.

Fortunately, Facebook&#x27;s C++ utility library, folly, has been Apache 2.0 since at least 2012 and never had the BSD+patent license put upon it.<a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;folly&#x2F;blob&#x2F;master&#x2F;LICENSE" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;folly&#x2F;blob&#x2F;master&#x2F;LICENSE</a>

Does any one know if this means react native is moving as well?Cause I might consider a move now.

I call it a win for the greater community of F&#x2F;OSS. Even Facebook cannot ignore us :-)

Are they only removing the clause on those packages and nothing else?

I think Vue is good competition for React. I think if React + Vue become the de facto standards then it&#x27;s a win for everyone. They&#x27;re both huge improvements for the web development experience.

Hopefully you are right. Competition is always good.

Long live vue&#x27;s chance at market domination!

Nice move! If you guys are still having trouble understanding these licenses, I recommend: <a href="https:&#x2F;&#x2F;choosealicense.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;choosealicense.com&#x2F;</a>

There are other popular Javascript packages that aren&#x27;t mentioned:<pre><code> dataloader
 draft-js
 express-graphql
 flux
 graphql-js
 regenerator
 relay
 yoga
</code></pre>
They&#x27;ll probably stick with BSD+Patents, unless the pressure is kept on, which is unfortunate.

Yeah I was wondering the same. Dual licensing should be strictly more permissive for users, who c=would be free to apply whichever terms gives them better protections.

&gt; Although we still believe our BSD + Patents license provides some benefits to users of our projectsI&#x27;m probably missing something, but: If their BSD+Patents was actually strictly &quot;better&quot; for the user, could they not just dual license under both? Is BSD+Patents ∪ MIT &lt; MIT for some reason?

Yangqing (creator and main author of Caffe&#x2F;Caffe2) here. We are moving to Apache 2.0 in a few days.

<a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;fb.resnet.torch&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;fb.resnet.torch&#x2F;blob&#x2F;master&#x2F;PATE...</a><a href="https:&#x2F;&#x2F;github.com&#x2F;caffe2&#x2F;caffe2&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;caffe2&#x2F;caffe2&#x2F;blob&#x2F;master&#x2F;PATENTS</a>

Flow is specifically mentioned in the linked release as getting rid of it...

According to the link posted, it looks like Flow will also be relicensed to MIT.

<a href="https:&#x2F;&#x2F;github.com&#x2F;facebook-atom&#x2F;atom-ide-ui&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook-atom&#x2F;atom-ide-ui&#x2F;blob&#x2F;master&#x2F;PAT...</a>

PyTorch itself isnt, But the multi-GPU version requires Gloo which is BSD+PATENTS<a href="https:&#x2F;&#x2F;github.com&#x2F;facebookincubator&#x2F;gloo&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebookincubator&#x2F;gloo&#x2F;blob&#x2F;master&#x2F;PATENT...</a>

From <a href="https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-react-s-license&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;112130496157735&#x2F;explaining-r...</a>&gt; As our business has become successful, we&#x27;ve become a larger target for meritless patent litigation. This type of litigation can be extremely costly in terms of both resources and attention. It would have been easy for us to stop contributing to open source, or to do what some other large companies do and only release software that isn&#x27;t used in our most successful products, but we decided to take a different approach.Never heard Facebook answer: why didn&#x27;t they just follow Red Hat&#x27;s model and make a &quot;Patent Promise&quot;[1]?Then accumulation of software patents would help deter meritless litigation while staying out of the way of FLOSS developers getting their work done.[1] <a href="https:&#x2F;&#x2F;www.redhat.com&#x2F;en&#x2F;about&#x2F;patent-promise" rel="nofollow">https:&#x2F;&#x2F;www.redhat.com&#x2F;en&#x2F;about&#x2F;patent-promise</a>

GraphQL has an ongoing discussion about this (that predates much of the recent flare ups about PATENTS): <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;graphql&#x2F;issues&#x2F;351" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;graphql&#x2F;issues&#x2F;351</a>The complicating factor there is Facebook actually has a patent covering the GraphQL specification (along with the fact that they&#x27;re applying PATENTS to a specification, vs an implementation): <a href="https:&#x2F;&#x2F;www.google.com&#x2F;patents&#x2F;US9646028" rel="nofollow">https:&#x2F;&#x2F;www.google.com&#x2F;patents&#x2F;US9646028</a>

A few more for your list: dataloader, draft-js, express-graphql, regenerator, relay, yoga

<a href="https:&#x2F;&#x2F;github.com&#x2F;facebookresearch&#x2F;faiss&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebookresearch&#x2F;faiss&#x2F;blob&#x2F;master&#x2F;PATENT...</a>

Rebound, their spring physics implementation for Android (Java) and the Web (JavaScript)

Please tell me more about commercial sales of GPL software. How could I make sure that people pay me for using my desktop app if it was GPL?

Are you a lawyer? If not, you would be doing a disservice to anyone curious about the topic.My own company&#x27;s lawyers consider the GPLv3 toxic and not allowed at all for company use in any software we create - that&#x27;s enough for me.

&gt;please take this time to at least consider GPL varients (A&#x2F;L&#x2F;GPLv3) for as much of your tooling as you possibly can. (perhaps CC0&#x2F;CCBY&#x2F;CCBYSA for content)I&#x27;m sorry but Creative Commons themselves declare that their licensing should not be used for software.<a href="https:&#x2F;&#x2F;creativecommons.org&#x2F;faq&#x2F;#can-i-apply-a-creative-commons-license-to-software" rel="nofollow">https:&#x2F;&#x2F;creativecommons.org&#x2F;faq&#x2F;#can-i-apply-a-creative-comm...</a>

&gt; Now that we have a concrete example of how picking tooling with bad licensing can bite people in the buttWhat are you referring to? Who has been bitten exactly?

&gt;I&#x27;ve been trying to tell everyone licensing is more important than they realize, but there are so many people who fundamentally misunderstand licensing and therefor just don&#x27;t careMaybe they don&#x27;t care because in reality its not a problem?In the sense that it&#x27;s not a problem people generally have -- not that nobody ever has had it.A lot of people worry too much about all kinds of BS eventualities and technicalities, and this could be one of them in most cases.&gt;Now that we have a concrete example of how picking tooling with bad licensing can bite people in the buttIt only bit FB in the butt (in the sense that some developers complained about their license choice) -- not those using the tooling with FB license.

I&#x27;ve been trying to tell everyone licensing is more important than they realize, but there are so many people who fundamentally misunderstand licensing and therefor just don&#x27;t care (dwtfyw license for example), or have falsely been trained by subpar instructors at uni and $othertraining about how bsd&#x2F;mit is the superior license for business because $reasons.The four freedoms and free software solve so many of the problems I see around modern tech-infrastructure. No, free software doesn&#x27;t solve every issue and has some of it&#x27;s own, for example I think at the code complexity levels we are at the many eyes theory is starting to crumble, but it doesn&#x27;t change the core truisms about freedom in computing that are important for us to move forward in a free and open society if we actually want to start solving prolems.Now that we have a concrete example of how picking tooling with bad licensing can bite people in the butt, please take this time to at least consider GPL varients (A&#x2F;L&#x2F;GPLv3) for as much of your tooling as you possibly can. (perhaps CC0&#x2F;CCBY&#x2F;CCBYSA for content)In my opinion, MIT&#x2F;BSD licenses like FB moved to in this case simply aren&#x27;t good enough to be future-proof, primarily because of the ability of future tivoization of a product that removes freedom from the user (think BSD on playstation).Remember, either the user controls the program, or the program controls the user.If the GPL scares you for some reason or you have question about it (commercial sales of gpl software for example), feel free to ask. I&#x27;ve spent enough time wading through just about every license so I think I might be able to cut through some fud.

We are moving to Apache 2.0 in a few days. Early draft at <a href="https:&#x2F;&#x2F;github.com&#x2F;Yangqing&#x2F;caffe2&#x2F;tree&#x2F;apache" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Yangqing&#x2F;caffe2&#x2F;tree&#x2F;apache</a> pending double check to make sure we are honoring all existing contributors.

Caffe2 machine learning <a href="https:&#x2F;&#x2F;github.com&#x2F;caffe2&#x2F;caffe2&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;caffe2&#x2F;caffe2&#x2F;blob&#x2F;master&#x2F;PATENTS</a>

The MIT license does not explicitly mention patents. However, depending on the lawyer, an argument could be made that it contains an implicit patent license. I think that Facebook would have an uphill battle arguing that their relicensing didn&#x27;t include patents after this kerfuffle.

I&#x27;m astounded how everyone things MIT == Apache2. MIT doesn&#x27;t protect you from patent litigation.This is a backwards move. Facebook is very good at PR painting this as a win for users.See <a href="http:&#x2F;&#x2F;en.swpat.org&#x2F;wiki&#x2F;Patent_clauses_in_software_licences#Apache_License_2.0" rel="nofollow">http:&#x2F;&#x2F;en.swpat.org&#x2F;wiki&#x2F;Patent_clauses_in_software_licences...</a>an explanation <a href="https:&#x2F;&#x2F;opensource.stackexchange.com&#x2F;a&#x2F;1890" rel="nofollow">https:&#x2F;&#x2F;opensource.stackexchange.com&#x2F;a&#x2F;1890</a>

So which FB project still have a BSD+patents license.I count:* ReasonML - <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;reason&#x2F;blob&#x2F;master&#x2F;PATENTS.txt" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;reason&#x2F;blob&#x2F;master&#x2F;PATENTS.txt</a>* GraphQL - <a href="https:&#x2F;&#x2F;github.com&#x2F;graphql&#x2F;graphql-js&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;graphql&#x2F;graphql-js&#x2F;blob&#x2F;master&#x2F;PATENTS</a>* react-native - <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react-native&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react-native&#x2F;blob&#x2F;master&#x2F;PATENTS</a>* PlanOut - <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;planout&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;planout&#x2F;blob&#x2F;master&#x2F;PATENTS</a>* Flow - <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;flow&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;flow&#x2F;blob&#x2F;master&#x2F;PATENTS</a>* Haxl - <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;Haxl&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;Haxl&#x2F;blob&#x2F;master&#x2F;PATENTS</a>* Flux - <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;flux&#x2F;blob&#x2F;master&#x2F;PATENTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;flux&#x2F;blob&#x2F;master&#x2F;PATENTS</a>Just a few that I found.. Please reply if you know more project that are still BSD+PATENTS licensed.

Yeah I think people are downvoting statements they disagree with...even when they add to the conversation. This is bad because those comments can disappear on HN.

So this post is getting downvoted, but no one is arguing why they disagree or believe this is not a realistic outlook. Emotional responses don&#x27;t really help anyone, and this is not Reddit.

Revoking a license retroactively is not possible.But since there is no patent grant with the MIT license, using the open source software is–potentially–open to patent litigation. I don’t think this has been tested in court yet.

&gt; FB would be able to counter-sue for copyright infringement due to the suing company&#x27;s use of FB&#x27;s open sourcethe whole point of mit&#x2F;bsd&#x2F;etc is copyright grant. fb can only realistically win a suit wrt infringement if they revoke the mit&#x2F;bsd license first (not sure if this is possible...not sure if it&#x27;s even been tried before).

What exactly doesn’t make sense? What in the theoretical scenario do you not understand?Here is the scenario without the … emotional baggage:——Company X has patent P.Company X releases open source O which provides implementation of patent P.There is no patent grant in the license of open source O.Company Y uses open source O.——Can company X sue company Y for infringement of patent P? I think the answer to this is “yes”.

Why would Facebook sue for copyright infringement? Suing them for patent infringement doesn&#x27;t invalidate the copyright - not for BSD+PATENTS, and certainly not for MIT. Your scenario doesn&#x27;t make sense.

IANAL, but here&#x27;s an ominous scenario:There is no patent clause now. Assuming some FB patent has crept its way in one of their open source, if a company sues FB for patent infringement, FB would be able to counter-sue for copyright infringement due to the suing company&#x27;s use of FB&#x27;s open source.&quot;As long as you don&#x27;t sue us, we won&#x27;t sue you&quot; kind of a deal. If the above scenario is true, it seems there is no de facto change beyond the political one.Anyone with more legal expertise able to disprove this scenario?

My guess is so that way when people talk about &quot;BSD-licensed Facebook software&quot; there won&#x27;t be any confusion as to whether it&#x27;s BSD or BSD + Patents.

Answering my own question:They replaced BSD with MIT, because the language used in the MIT license is closer to what constitutes a patent grant: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;MIT_License#Comparison_to_other_licenses" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;MIT_License#Comparison_to_othe...</a>

Why replace BSD + patent grant with MIT, instead of keeping BSD alone without a patent grant?

Every time I make a negative comment about React, I get a ton of downvotes. So this time, I&#x27;d like to applaud the React legal team for this momentous decision. I will now consider using React in future projects.But I&#x27;ll still look for a framework with better separation of view and controller logic. And incremental DOM.

Reminder that FB had already relicensed RocksDB following <a href="https:&#x2F;&#x2F;issues.apache.org&#x2F;jira&#x2F;browse&#x2F;LEGAL-303" rel="nofollow">https:&#x2F;&#x2F;issues.apache.org&#x2F;jira&#x2F;browse&#x2F;LEGAL-303</a>

This looks like damage control and is limited to a select few open source projects of theirs. Feel free to change your mind, but think twice about committing to depend on projects from a source that didn&#x27;t seem to have a problem with this license before the exodus. Will it happen again?

But my understanding is that some patent grant is better than no patent grant. The controversy was about the termination clause favouring Facebook, but it’s still better than not having it. Surely the only true solution would have been to switch to a license that has a more liberal patent grant, eg Apache 2?

React 16 will be licensed under MIT. Previous versions of React which you may be using under BSD+patents will remain licensed under BSD+patents. If you upgrade to 16, you should be free and clear of the patents clause. Definitely not PR theater.(IANAL, but this is how relicensing works basically universally)

Since i&#x27;m not a lawyer, I have questions...The patents grant was irrevocable except under explicitly described conditions. A license change wasn&#x27;t one of these conditions.So:1) Does the patent grant still apply? i.e. is it now MIT + Patents?2) If yes&#x2F;no, what about existing users of React? i.e. if you were a user up to the point of the license change, do you get the grant, but new users don&#x27;t?3) Doesn&#x27;t not having the grant make us worse off? Presumably only the Apache 2 license would be an improvement in this regard?4) Is this all just PR theater?

Relicensing React, Jest, Flow, and Immutable.js