Relicensing React, Jest, Flow, and Immutable.js
51–60 of 528 posts
Re: Relicensing React, Jest, Flow, and Immutable.js
#52Re: Relicensing React, Jest, Flow, and Immutable.js
#53Why not Apache 2.0 though? That would have been a logical choice.
Re: Relicensing React, Jest, Flow, and Immutable.js
#54What about GraphQL?
Is the GraphQL spec itself under the BSD+patents clause? Or just their specific implementation? Couldn’t somebody like the Apollo crew create their own implementation if necessary?
The issue with the GraphQL spec is that people actually want a patent grant for alternative implementations, but there isn't one.
Re: Relicensing React, Jest, Flow, and Immutable.js
#55Earlier quoted context omitted.
It’s asymmetrical in the sense that your license terminates even if you sue them for something that’s not in the software you’re using. I.e. they rip off your feature, and you’re using React, you’re f##d.
Literally not true. You’d just revert to BSD if you sued. So same protection as now.
Re: Relicensing React, Jest, Flow, and Immutable.js
#56Thank you, Wordpress.[1] [1] https://ma.tt/2017/09/on-react-and-wordpress/
Re: Relicensing React, Jest, Flow, and Immutable.js
#57That was incredibly unexpected. Facebook may very well end up in the majority's good graces with this move. I wonder how some of the bigger players will react (no pun intended) after their abandonment of React in lieu of Vue or some other framework. Interesting times indeed.
Re: Relicensing React, Jest, Flow, and Immutable.js
#58Re: Relicensing React, Jest, Flow, and Immutable.js
#59That was incredibly unexpected. Facebook may very well end up in the majority's good graces with this move. I wonder how some of the bigger players will react (no pun intended) after their abandonment of React in lieu of Vue or some other framework. Interesting times indeed.
Really? They are doing the minimum possible to prevent an exodus from their stack after a public outcry.