News for hackers. Stuff that matters.
Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Friday September 22, 2017 @06:26PM (#15316453)
So... I guess I still don't understand what was wrong with BSD+Patents.

I get that there'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'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's (and others') implementation of it might have left something to be desired, and they're certainly a large company with a lot of resources behind them, so the power dynamic might be a bit lopsided, but...

Well, let's just say I'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'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'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's language includes an implicit patent grant, but I don't believe that's a settled matter.

Re:Relicensing React, Jest, Flow, and Immutable.js by Lazare on Saturday September 23, 2017 @01:03AM (#15318227)
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'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's no patent issue, and put our heads in the sand.

4. But Facebook's BSD+Patents license made us think about patents. Nobody stopped and said "can we use Angular? Are there patents on core elements of it?". 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'd have to deal with is toilets blocked with shit, and not software patents, which are much worse.

5. Now that it's under an MIT license it's just as dangerous to use React (maybe more) but we can pretend it's safe again.

Notice that Wordpress'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.)

Re:Relicensing React, Jest, Flow, and Immutable.js by chrisco255 on Saturday September 23, 2017 @02:11AM (#15318422)
This. I don't even want to know how many patents we're all infringing on in everything we ship. We all just sort of sweep this under the rug. No one ever does a technical/patent analysis. Is patent check part of your deployment pipeline? I highly doubt it. There'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.
Re:Relicensing React, Jest, Flow, and Immutable.js by lukaszsamson on Saturday September 23, 2017 @06:49AM (#15319161)
I have one counter example. I used to work at Samsung's R&D a few years ago and there patent analysis (and filing patents) was obligatory for every developer. They had been bitten by lawsuits a few times so they learned.
Re:Relicensing React, Jest, Flow, and Immutable.js by cjbprime on Sunday September 24, 2017 @11:28AM (#15325039)
You're actually discouraged from conducting that patent analysis, since damages are trebled for willful infringement.
Re:Relicensing React, Jest, Flow, and Immutable.js by matt4077 on Saturday September 23, 2017 @12:29PM (#15320422)
The sad thing is that Facebook's policy was obviously informed by exactly this point of view, that, essentially, software should not be patented.

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

Re:Relicensing React, Jest, Flow, and Immutable.js by dtzur on Saturday September 23, 2017 @02:17AM (#15318429)
"and the more you think about patents the more you wish you were a plumber and not a dev so all you'd have to deal with is toilets blocked with shit, and not software patents, which are much worse."

This.

Re:Relicensing React, Jest, Flow, and Immutable.js by ploxiln on Friday September 22, 2017 @06:54PM (#15316650)
If it's licensed MIT, the Engineers just say "it's MIT license like half of the libraries we already use" and it'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's a disaster. They're very risk-adverse and no one's really sure what will happen when it gets to court. It doesn't have to make sense - after all, most software patents don't make sense, and most software patent lawsuits don'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'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't notice you. Any language about patents adds complications which no one wants to figure out.

Re:Relicensing React, Jest, Flow, and Immutable.js by carussell on Friday September 22, 2017 @07:41PM (#15316946)
This is the first time I've seen "put your head in the sand" as an actual recommendation, instead of being characterized as something not to do. And as far as recommendations go, it's more than a little bit nutty.
Re:Relicensing React, Jest, Flow, and Immutable.js by wrs on Friday September 22, 2017 @11:17PM (#15317882)
Not at all. Willful infringement is grounds for triple damages. So "never, ever, ever look at patents unless an attorney asks you to" was the company policy at Microsoft and Apple when I was there, and at several other major tech companies whose policies I happen to have heard of. If you were to mention to a company attorney that you've looked at another entity's patent, there would be a loud screeching noise from the attorney and you'd be scheduled for an immediate refresher course on patent policy.
Re:Relicensing React, Jest, Flow, and Immutable.js by slaymaker1907 on Saturday September 23, 2017 @12:16AM (#15318073)
Isn't the point of the patent system supposed to be to encourage people to open up ideas for general use instead of hoarding them?
Re:Relicensing React, Jest, Flow, and Immutable.js by saghm on Saturday September 23, 2017 @12:50AM (#15318173)
Yes, but that doesn't mean it's necessarily successful at it
Re:Relicensing React, Jest, Flow, and Immutable.js by Eridrus on Saturday September 23, 2017 @08:07AM (#15319363)
Maybe at one point, I don't think any policy person has thought this in a long time though.
Re:Relicensing React, Jest, Flow, and Immutable.js by chc on Friday September 22, 2017 @08:02PM (#15317077)
It's actually a common policy when it comes to patents. If you are found to infringe on a patent and it can be shown that you knew about it, the penalties are much harsher. This is one of the many reasons people consider the patent system to be badly broken.
Re:Relicensing React, Jest, Flow, and Immutable.js by jakelazaroff on Friday September 22, 2017 @10:04PM (#15317618)
Is there no similar penalty for intentionally foregoing due diligence specifically to avoid harsher penalties?
Re:Relicensing React, Jest, Flow, and Immutable.js by Lazare on Saturday September 23, 2017 @01:21AM (#15318284)
There is not. If you know the patent exists, you get higher (I think triple?) damages. If you don't, you don't. And you have no obligation to check.

Example: There is a patent in the US on ordering food from a menu online. It's held by a NPE (aka, a patent troll), and they charge a fairly high license fee. Some people who offer online ordering to restaurants pay the license fee; others don't. If you don't pay, then you can afford to charge lower prices than your competitors. If you do pay, then it's in your interests to tell everyone you meet about the patent, because every person you tell is someone who now faces triple damages if they opt to use on your your non-paying competitors.

Let me say that again, because it's so crazy: Some companies actually advertise their high prices, because a potential customer just reading their pricing page can thereafter no longer opt for a lower priced competitor without being subject to increased damages.

Re:Relicensing React, Jest, Flow, and Immutable.js by rocqua on Saturday September 23, 2017 @06:35AM (#15319124)
In some sense, reading this comment is actually harmful. I now know of that patent, so would be subject to triple damages.
Re:Relicensing React, Jest, Flow, and Immutable.js by optimuspaul on Saturday September 23, 2017 @02:19PM (#15320951)
Good god how is that even patentable?? That's not at all novel.
Re:Relicensing React, Jest, Flow, and Immutable.js by mort96 on Sunday September 24, 2017 @11:40AM (#15325092)
Neither novelity nor lack of prior art are requirements for getting a patent, it seems. If a patent has prior art, or is incredibly obvious, that might help your case in court if you're getting sued, but if you're an individual or small company getting sued for patent infringement by a company with an army of lawyers, you've already lost.
Re:Relicensing React, Jest, Flow, and Immutable.js by chc on Friday September 22, 2017 @10:41PM (#15317746)
AFAIK, no. I don't know of any case law that says the reason you were unaware of the patent is relevant; just whether the infringement was "willful" — one component of which being knowledge of the patent.
Re:Relicensing React, Jest, Flow, and Immutable.js by ballenf on Friday September 22, 2017 @07:09PM (#15316763)
And at small to medium-sized businesses, they don'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.
Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Saturday September 23, 2017 @05:31AM (#15318951)
So, in other words, what you're effectively saying is that everyone'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't want to deal with it?

That's... sad.

> Being aware of patents ... makes punitive damages worse.

Sure, but that doesn't have anything to do with a BSD+Patents license. The license doesn't say "you also must do extensive patent research when using our software". You have to actually be aware of the patents that you're infringing to be held liable for extra damages.

Re:Relicensing React, Jest, Flow, and Immutable.js by mort96 on Sunday September 24, 2017 @11:46AM (#15325113)
An argument I've read is that MIT and BSD are widely understood to give an implicit patent grant, and Facebook's explicit grant overrides the implicit one, and Facebook's is more restrictive than the implicit one because you lose that patent grant if you ever try to sue Facebook.

Also, IANAL, so I may be entirely wrong.

Re:Relicensing React, Jest, Flow, and Immutable.js by ngrilly on Friday September 22, 2017 @07:39PM (#15316933)
I don't get your point about MIT licensed being a standard. The BSD license used by React is a standard too.
Re:Relicensing React, Jest, Flow, and Immutable.js by karlshea on Friday September 22, 2017 @08:18PM (#15317185)
But BSD+Patents isn't.
Re:Relicensing React, Jest, Flow, and Immutable.js by ngrilly on Saturday September 23, 2017 @05:19AM (#15318929)
What I meant is that Facebook could just have used BSD without a patent grant.

But I read in other comments that some some lawyers think MIT implies a patent grant, which could explain why they switched from BSD to MIT.

Re:Relicensing React, Jest, Flow, and Immutable.js by karlshea on Saturday September 23, 2017 @01:33PM (#15320753)
> What I meant is that Facebook could just have used BSD without a patent grant.

Ahh, I see. But I think if they were just using BSD instead of BSD+Patents no one would have had any issue with it.

Re:Relicensing React, Jest, Flow, and Immutable.js by spenczar5 on Friday September 22, 2017 @07:30PM (#15316880)
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's patent clause disarms all their opponents, but leaves them free to attack. It'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's why it's totally unpalatable, at least at the big companies.

Re:Relicensing React, Jest, Flow, and Immutable.js by jaredklewis on Friday September 22, 2017 @09:10PM (#15317415)
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.
Re:Relicensing React, Jest, Flow, and Immutable.js by slaymaker1907 on Saturday September 23, 2017 @12:18AM (#15318080)
Only over the React patents. They could, however, sue you over your VR system or something but leave you little recourse due to not wanting to lose your React/other FB patent grants.
Re:Relicensing React, Jest, Flow, and Immutable.js by jaredklewis on Saturday September 23, 2017 @02:58AM (#15318556)
Nope. The PATENTS file specifically says that if Facebook initiates patent litigation (related or unrelated to React) you can counter sue Facebook AND keep your React patent grant.

"...if Facebook or any of its subsidiaries or corporate affiliates files a lawsuit alleging patent infringement against you in the first instance, and you respond by filing a patent infringement counterclaim in that lawsuit against that party that is unrelated to the Software, the license granted hereunder will not terminate under section (i) of this paragraph due to such counterclaim."

Re:Relicensing React, Jest, Flow, and Immutable.js by lftl on Saturday September 23, 2017 @10:06AM (#15319777)
The only legitimate criticism I've heard of the FB patent grant is that FB could intentionally infringe your patents and the you couldn't sue them for infringement without losing your React patent grant. It's such a narrow case though that I seriously doubt it's a legitimate concern for most of the people complaining about it.
Re:Relicensing React, Jest, Flow, and Immutable.js by dllthomas on Monday September 25, 2017 @07:40PM (#15335066)
And you can stop using React, then sue. Even if they also stop using your patent, they were in violation when they used it. They can't retroactively put you in violation with their revocation.

Moreover, nothing is preventing you from informing them of your patent and asking that they stop using it. If they continue to, it's clearly willful infringement.

Re:Relicensing React, Jest, Flow, and Immutable.js by rhinoceraptor on Saturday September 23, 2017 @03:04PM (#15321122)
What React patents are there? And it seems to me that using Preact/Vue/etc would not be any better than using React if in fact there are patented technologies in React.
Re:Relicensing React, Jest, Flow, and Immutable.js by mort96 on Sunday September 24, 2017 @11:52AM (#15325147)
Is there _any_ technology that isn't covered by some patent? I would imagine virtually every library we use unknowingly infringes on dozens of patents.
Re:Relicensing React, Jest, Flow, and Immutable.js by blktiger on Saturday September 23, 2017 @06:50PM (#15322216)
It'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'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.

Re:Relicensing React, Jest, Flow, and Immutable.js by ec109685 on Sunday September 24, 2017 @06:10PM (#15326753)
Why would you immediately have to recall your software? Facebook would have to have counter sued you for some hypothetical patent they have for React first and “recall all your software” would have had to be the court ordered remedy.
Re:Relicensing React, Jest, Flow, and Immutable.js by blktiger on Tuesday September 26, 2017 @11:28AM (#15339493)
True, they would have to counter-sue but you don't think they would in that situation? Technically your license is invalid and if you have _shipped_ software to customers that is violating the license is it not?
Re:Relicensing React, Jest, Flow, and Immutable.js by ec109685 on Friday October 06, 2017 @01:44AM (#15414678)
Suing Facebook does not invalidate your license to use their software and source code. The BSD license still applies after you sue Facebook. It can’t be taken away.
Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Saturday September 23, 2017 @05:38AM (#15318965)
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'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's that you are using, then your license to use FB's software is NOT terminated. That's actually entirely reasonable and great.

Re:Relicensing React, Jest, Flow, and Immutable.js by chrisco255 on Saturday September 23, 2017 @02:14AM (#15318425)
No, they said your license didn't terminate if you had a counterclaim against them. The only event that license terminated was if YOU attacked Facebook.
Re:Relicensing React, Jest, Flow, and Immutable.js by nilliams on Saturday September 23, 2017 @08:21AM (#15319414)
> The only event that license terminated

Patent grant terminated, not license

Re:Relicensing React, Jest, Flow, and Immutable.js by aljones on Friday September 22, 2017 @09:25PM (#15317465)
But it wasn't unpalatable at Google, MS, Apple and many other large companies.
Re:Relicensing React, Jest, Flow, and Immutable.js by paulddraper on Tuesday September 26, 2017 @12:33AM (#15336196)
Hasn't that already happened?

Oracle v. Google?

Re:Relicensing React, Jest, Flow, and Immutable.js by SwellJoe on Friday September 22, 2017 @06:38PM (#15316538)
I think it's more about the complexity of licensing, patents, and the uncertainty a new license presents.

Using a license that'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'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'll still be true? I'd bet on it, but I also won't be shocked if something dramatic happens. Sun looked pretty unassailable through the 80s and 90s, and then they didn'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's coming from.)

Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Saturday September 23, 2017 @05:44AM (#15318979)
By that logic we'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't be afraid of it just because it's new. People had problems with GPLv3 when it came out, but those problems were about specific parts of the license, not "oh god it's new and scary and we don't know how to interpret it". And that's the GPL, a license orders of magnitude more complex than BSD+Patents.

As an aside, I realized I read FB'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.

Re:Relicensing React, Jest, Flow, and Immutable.js by madeofpalk on Saturday September 23, 2017 @06:54AM (#15319173)
As summed up my Dan Abramov: https://twitter.com/dan_abramov/status/911397710791667712

> 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

Re:Relicensing React, Jest, Flow, and Immutable.js by creatonez on Saturday September 23, 2017 @08:53PM (#15322641)
The root problem is that it's a revocable license. This arguably makes it not a free software license at all.
Re:Relicensing React, Jest, Flow, and Immutable.js by guelo on Friday September 22, 2017 @07:26PM (#15316856)
Unethical developers that work at shitty companies with shitty lawyers were annoyed that they couldn't use React. That'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.

Re:Relicensing React, Jest, Flow, and Immutable.js by nemothekid on Friday September 22, 2017 @08:00PM (#15317069)
>Unethical fevelopers that work at shitty companies with shitty lawyers were annoyed that they couldn't use React. That'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.

Re:Relicensing React, Jest, Flow, and Immutable.js by spenczar5 on Friday September 22, 2017 @07:33PM (#15316896)
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't sue them. It would be a much, much worse patent regime.
Re:Relicensing React, Jest, Flow, and Immutable.js by chc on Friday September 22, 2017 @08:07PM (#15317116)
The entire point of the patent license is that they can't sue you for violating any patents that cover the library you're using. So it's at least a bit over-broad to it puts all the power in their hands.
Re:Relicensing React, Jest, Flow, and Immutable.js by cheald on Friday September 22, 2017 @10:00PM (#15317605)
The problem with the patent clause was that it prevented you from suing Facebook for any patent infringement, even if it's unrelated to React. If you're a React using-company, this more or less meant that Facebook had carte blanche to infringe on any your patents at will in an exchange for a license to use their React patents. That's a quite one-sided deal.
Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Saturday September 23, 2017 @05:45AM (#15318981)
No they can't, actually. The language in BSD+Patents only terminates your license to use the software if you are the aggressor in a patent suit. If you simply counter-sue because FB sued you, you're in the clear.
Re:Relicensing React, Jest, Flow, and Immutable.js by guelo on Friday September 22, 2017 @07:38PM (#15316929)
If BSD+patent was widely adopted it could disarm all sides equally.
Re:Relicensing React, Jest, Flow, and Immutable.js by eridius on Friday September 22, 2017 @07:56PM (#15317037)
No, it only puts power in the hands of the big players. It might mean the big players can't sue each other, but they can absolutely sue the smaller companies. BSD + Patents only "disarms" anyone who's actually using the licensed software, and perhaps more importantly, depending on it to the extent that they can't reasonably move away if they lose the patent grant. Even if Facebook did start using OSS from some small company, they could probably just rewrite the software themselves if they want to sue the company.
Re:Relicensing React, Jest, Flow, and Immutable.js by cbhl on Friday September 22, 2017 @08:21PM (#15317199)
Both Facebook and Google's lawyers want to create a world where software patents don't block innovation.

BSD + Patents doesn't look like the way we'll get there. Is there a way we can get there without putting "power in the hands of the big players" in the interim?

Re:Relicensing React, Jest, Flow, and Immutable.js by guelo on Friday September 22, 2017 @08:14PM (#15317158)
Patents offer small companies no protection in a dispute with a large company. The legal fight is too expensive.
Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Saturday September 23, 2017 @05:46AM (#15318985)
No it doesn't; read the license again. It disarms you from being the aggressor; if FB comes after you, you keep your right to counter-sue while also keeping your license to use the software.
Re:Relicensing React, Jest, Flow, and Immutable.js by SpaceNugget on Saturday September 23, 2017 @07:41AM (#15319298)
Yes it does, Them using patents that you don't grant them and you being unable to sue them for it is definitely putting the power in their hands.
Re:Relicensing React, Jest, Flow, and Immutable.js by vectorjohn on Saturday September 23, 2017 @02:55PM (#15321090)
Yes, that's exactly the point. It disarms people from fighting over patent nonsense. If you hate software patents you should love the bad + patents license.
Re:Relicensing React, Jest, Flow, and Immutable.js by ec109685 on Sunday September 24, 2017 @06:15PM (#15326778)
Facebook could never take away your license to the software. BSD license was irrevocable, whether you sued them or not.
Re:Relicensing React, Jest, Flow, and Immutable.js by zanny on Friday September 22, 2017 @08:01PM (#15317070)
It already exists and is called the Apache license. If you want to disarm patent trolls but don't want to compel the preservation of user freedoms on other distributors of your software license it ALv2.
Re:Relicensing React, Jest, Flow, and Immutable.js by spenczar5 on Friday September 22, 2017 @08:33PM (#15317255)
No, it would disarm the group whose software is used by everyone else. If you're a small company, it's not likely that you have written stuff that Facebook uses. So, that world looks like one where all big companies are untouchable, but they can easily pick on small companies. Really not good.
Re:Relicensing React, Jest, Flow, and Immutable.js by kelnos on Saturday September 23, 2017 @05:47AM (#15318987)
Nope. See other replies. The license termination clause only goes into effect if you as the user of the software are the initial aggressor in a patent suit.
Re:Relicensing React, Jest, Flow, and Immutable.js by reustle on Friday September 22, 2017 @07:52PM (#15317016)
Maybe that's so but do you really think you can change the license or all open source projects from companies? That's a fantasy.