Live data from Hacker News

Relicensing React, Jest, Flow, and Immutable.js

code.facebook.com

361–370 of 528 posts

Re: Relicensing React, Jest, Flow, and Immutable.js

#361
Of this happens, it will be the major turning point of React + JSX "winning" the frontend world.

Another one is tooling, but the recent typescript Compiler can do TSX natively (no webpack config etc required).

The last one is size/performance, but afaik the guy behind inferno is now working on react, this all should union React's "forks" into a single force.

Interesting times we live in, lets hope that facebook does not fail on this.

Re: Relicensing React, Jest, Flow, and Immutable.js

#362

Earlier quoted context omitted.

Can somebody who speaks legalese translate Red Hat's Patent Promise into more parseable English? I'm curious how it works, but the wording is pretty obscure to me.

I am not a lawyer, but my take on it is: Red Hat holds patents but promises not to enforce them. This means anyone can use the IP without worrying about being sued for infringement. No one else can claim they own the IP because Red Hat already owns it. They also have a clause saying that if Red Hat sells the IP, the buyer needs to uphold the same promise.

I am also not a lawyer. But I don't think a "promise" is a legally enforceable concept.

Re: Relicensing React, Jest, Flow, and Immutable.js

#363
post #261
post #120

Earlier quoted context omitted.

Furthermore, suppose you'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'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 t…

> 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're completely f cked. Maybe, maybe not. You suing them over your patent would terminate you patent* license from Facebook, but not your copyright license. Whether that fucks you or not depends on whether or not you actually NEED a patent license from Facebook. As far…

There is - its been posted multiple times https://www.google.com/patents/US20170221242.

Re: Relicensing React, Jest, Flow, and Immutable.js

#364

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

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't even relicense under MIT one of the de facto open source licenses without being met with suspicion.

They have the patent: https://www.google.com/patents/US20170221242. Just MIT is a good option, I don't really understand why they don't want to "fix" the patent grant to be like Apache 2.0 or Google's. Why relicense everything when fixing 1 sentence would fix the problem completely.

Re: Relicensing React, Jest, Flow, and Immutable.js

#365
post #248

Earlier quoted context omitted.

Those websites weren't leaving, they never arrived..

They were close to arriving but they backtracked, all 25% of them. I'd call that an exodus before you even arrive.

You can't die if you were never alive to begin with

Re: Relicensing React, Jest, Flow, and Immutable.js

#366

Earlier quoted context omitted.

I am not a lawyer, but my take on it is: Red Hat holds patents but promises not to enforce them. This means anyone can use the IP without worrying about being sued for infringement. No one else can claim they own the IP because Red Hat already owns it. They also have a clause saying that if Red Hat sells the IP, the buyer needs to uphold the same promise.

I am also not a lawyer. But I don't think a "promise" is a legally enforceable concept.

I'm not a lawyer either, but the estoppel doctrine should make it enforceable.

Re: Relicensing React, Jest, Flow, and Immutable.js

#368
post #140

So which FB project still have a BSD+patents license. I count: * ReasonML - https://github.com/facebook/reason/blob/master/PATENTS.txt * GraphQL - https://github.com/graphql/graphql-js/blob/master/PATENTS * react-native - https://github.com/facebook/react-native/blob/master/PATENTS * PlanOut - https://github.com/facebook/planout/blob/master/PATENTS * Flow - https://github.com/facebook/flow/blob/master/PATENTS * Haxl…

I'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't care (dwtfyw license for example), or have falsely been trained by subpar instructors at uni and $othertraining about how bsd/mit is the superior license for business because $reasons. The four freedoms and free software solve so many of the pr…

[deleted]

Re: Relicensing React, Jest, Flow, and Immutable.js

#369

Earlier quoted context omitted.

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

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

When has this ever happened?
Post reply on HN