News for hackers. Stuff that matters.
Re:Relicensing the GraphQL specification by jonas21 on Tuesday September 26, 2017 @02:15PM (#15341218)
So, wait, let me get this straight:

React has a revokable patent grant, people freak out about it, FB removes the patent grant, everyone rejoices.

GraphQL doesn't have a patent grant, people freak out about it, FB adds a revokable patent grant, everyone rejoices.

What am I missing?

Re:Relicensing the GraphQL specification by slavik81 on Tuesday September 26, 2017 @03:29PM (#15341774)
For one, the problem with React was with the specific limitations and conditions of Facebook's patent grant. These are completely different terms, so I don't see why you'd expect the same response.

Additionally, React is software while GraphQL is a specification. Different types of works require different types of licenses.

The BSD license says I can use the thing being licensed. With a library like React, it's pretty clear what 'use' means. By 'use', they mean they want to allow me to build software with it, so they're granting me all rights necessary to do that. With a specification, though? What does it mean that it grants me the right to use it? There's lots of things you might do with a specification. Did they intend to allow me to implement my own version? If they didn't, I might not have all the rights I need to do so.

DannyBee, an actual lawyer, talked briefly about the importance that this is a specification when this topic first came up: https://news.ycombinator.com/item?id=15291330

Re:Relicensing the GraphQL specification by slaymaker1907 on Tuesday September 26, 2017 @02:19PM (#15341265)
This patent grant seems at first glance to be much less aggressive than BSD+patents. It seems to only work if the patent claim being filed is related to GraphQL.
Re:Relicensing the GraphQL specification by randallsquared on Tuesday September 26, 2017 @02:24PM (#15341311)
> What am I missing?

That there is a patent actually associated with GraphQL, I believe.

Re:Relicensing the GraphQL specification by abiox on Tuesday September 26, 2017 @03:05PM (#15341605)
the funny thing is, this means that the patent grant previously shipped with react had basically zero relevance to using react (even after a patent dispute).
Re:Relicensing the GraphQL specification by seangrogg on Tuesday September 26, 2017 @03:29PM (#15341783)
Yes, as was pointed out by the many that continued to use React.
Re:Relicensing the GraphQL specification by raulk on Tuesday September 26, 2017 @03:29PM (#15341775)
Graph query logic (US 9646028 B2)

https://www.google.com/patents/US9646028

Re:Relicensing the GraphQL specification by hetspookjee on Tuesday September 26, 2017 @03:40PM (#15341887)
I don't understand how this can be a patent. I seem to be infringing on the patent every day whenever I try to navigate through xmls and json files with a friendly API. Can anyone shed some light on how this patent is innovative?
Re:Relicensing the GraphQL specification by abiox on Tuesday September 26, 2017 @04:03PM (#15342056)
it's a commonly held view that software patents are almost entirely garbage.
Re:Relicensing the GraphQL specification by graphememes on Tuesday September 26, 2017 @04:24PM (#15342201)
you can remove the almost from that sentence.
Re:Relicensing the GraphQL specification by tzs on Tuesday September 26, 2017 @08:39PM (#15343938)
There is a patent application associated with React.

https://www.google.com/patents/US20170221242

Re:Relicensing the GraphQL specification by zokier on Tuesday September 26, 2017 @04:04PM (#15342067)
This comment sums the situation up pretty nicely: https://news.ycombinator.com/item?id=15318227
Re:Relicensing the GraphQL specification by paxy on Tuesday September 26, 2017 @02:37PM (#15341418)
The core problem is ambiguity, and so any step towards reducing it is good.
Re:Relicensing the GraphQL specification by beefsack on Tuesday September 26, 2017 @09:14PM (#15344120)
One is an implementation, the other is a standard which others can implement. Each is licensed differently.
Re:Relicensing the GraphQL specification by abiox on Tuesday September 26, 2017 @03:09PM (#15341627)
some people were pushing the unfounded idea that one's usage of react would somehow be impacted by the patent grant.

but as you perhaps allude to... people's use of graphql will be impacted by the patent grant. so back to square one?

Re:Relicensing the GraphQL specification by kbenson on Tuesday September 26, 2017 @03:17PM (#15341683)
> some people were pushing the unfounded idea that one's usage of react would somehow be impacted by the patent grant.

The idea wasn't unfounded, it was untested. People had worries because of how it looked like it could be used, and people with legal experience that weighed in seemed to have differing opinions on the possible impact. That was a foundation for concern.

Re:Relicensing the GraphQL specification by abiox on Tuesday September 26, 2017 @03:23PM (#15341730)
react isn't covered by fb patent. therefore the patent grant could not impact it, by definition (fb even said this, multiple times).

if fb wanted to stop react use, they would simply revoke the copyright grant.

in the end, all that was accomplished is that react users became less safe, not more.

Re:Relicensing the GraphQL specification by slavik81 on Tuesday September 26, 2017 @03:37PM (#15341863)
When and where did Facebook say that React did not implement anything covered under any Facebook patents?
Re:Relicensing the GraphQL specification by abiox on Tuesday September 26, 2017 @03:50PM (#15341962)
what matters are whether patents are registered (public data), not what fb claims.

removing the patent grant only means you are less safe in terms of patents (fb can initiate a suit without penalty), and no more safe in terms of react usage (fb can still revoke your copyright grant at their discretion).