This GraphQL situation is different and, arguably, somewhat worse than the ReactJS BSD+Patent license issue.
The problem here is the GraphQL specification doesn't have a patent grant (unlike ReactJS, which does, but people don't like the terms of the grant). And Facebook have filed a patent for GraphQL (https://www.google.com/patents/US9646028) that has some quite broad language.
Due to the patent, and the lack of a patent grant, most GraphQL users likely infringe on Facebook's patents.
Please read: https://medium.com/@dwalsh.sdlr/using-graphql-why-facebook-n...
That post has text of the patents in question. Please warn if you're linking to text of patents so people don't expose themselves to triple damages.
I'm not sure if the author of that article is partially trolling in the attempt to get Facebook's patents terms applied to the entire spec.
The best solution would be to abolish software patents completely.
I think this entire PATENTS situation with Facebook is a good reason why people should prefer Free software that is created and managed by individual developers and independent foundations over "open source" software produced by large companies with legal teams and dubious agendas.
[1] http://en.swpat.org/wiki/Patent_clauses_in_software_licences...
TL;DR - In 2012, Yahoo sued Facebook over 10 patents, "general sentiment in the industry was that the lawsuit against Facebook was without merit; some said Yahoo was a patent troll." Facebook spent a lot of money acquiring a patent warchest to be used defensively against patent suits in the future. Yahoo then drops the patent infringement case.
"The key thing to understand is that Facebook used and invested in patents as an important way to defend itself."
Facebook asserts that anyone can use these open source libraries with a patent use grant. However, if that company then sues Facebook over patent infringement, Facebook reserves the right to revoke all patent grants so they can use their own patents in a countersuit.
I can see how it makes sense for Facebook, but still a toxic effect on the actual "open source" status of React et al.
That's the definition of toxic.
In more concrete terms, if you see some project is licensed under Apache 2.0, then you can still be sued for using it, because while you may have a guarantee that its contributors won't sue you, it doesn't make anybody else's patents go away.
In slightly more concrete terms than that, if Project X causes Facebook to be sued by Corp Y because Facebook is using that project, then Facebook has no protection if it is not a Corp Y project nor have they ever contributed to it.
In real life, Corp Y is Yahoo, who sued Facebook several years ago on a bunch of patent-related matters. Facebook then went on a tear building up a war chest and crafting the PATENTS text so that it could never happen again.
So if fb just uses something patented by my company in one of their products, just uses it without my company's permission, but doesn't sue, what is my company's recourse?
What is my company's leverage or incentive to get them to pay my company for a license?
You assume an intent but the intent is unclear here. React is an incredibly attractive technical product. As a web dev at my company I really want to use it, but had I not realized its strange underhanded bidirectional patent grant and evangelized it I could have boxed my company into a corner, forcing it to decide to sacrifice our React web infrastructure or defend our patents.
Spreading misinformation about the danger only serves to undermine the OSS community's response.