Live data from Hacker News

Relicensing React, Jest, Flow, and Immutable.js

code.facebook.com

161–170 of 528 posts

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

#161
post #126

>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/libraries I choose for work and personal use.

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

Most of React's competitors are licensed MIT I'm curious what you think folks should switch to.

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

#163

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.

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

Huh? Where have you been for the last month or two?

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

#166
post #160

Earlier quoted context omitted.

> Because their licence gave Facebook the upper hand if they wanted to come after you. No it didn't. Facebook made a nothing-up-the-sleeve showing; you had recourse if they decided to "come after you", because your right to countersue was something that was explicitly protected in the PATENTS grant. Removing the grant, on the other hand, contributes to a world where everyone else can come after you. That should be sc…

Wasn't the issue not "if they come after you" but "if they pirate your tech without suing you"?

[deleted]

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

#167

Earlier quoted context omitted.

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

Not at all. There was an exodus brewing. For starters: https://ma.tt/2017/09/on-react-and-wordpress/ https://hacks.hyperspacer.com/app/items/15256532

An HN thread with a dozen responses? Hardly an exodus.

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

#168

Thank you, Wordpress.[1] [1] https://ma.tt/2017/09/on-react-and-wordpress/

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

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

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

#169
Every time I make a negative comment about React, I get a ton of downvotes. So this time, I'd like to applaud the React legal team for this momentous decision. I will now consider using React in future projects.

But I'll still look for a framework with better separation of view and controller logic. And incremental DOM.

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

#170
post #155

Earlier quoted context omitted.

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.

If BSD+patent was widely adopted it could disarm all sides equally.

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.
Post reply on HN