Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Relicensing React, Jest, Flow, and Immutable.js

code.facebook.com

Post reply on HN
Print view View original

421–430 of 528 posts

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

#421

Post by mlsarecmg »

irrational wrote: post #185
blaqkangel wrote: post #11

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

Yeah, we've already settled on Vue (because our lawyers forbade us from using React), but now I'm sure they would approve React. So... do we abandon our work on Vue (which so far is amazing) to switch to React since the React ecosystem is so large, or do we stay the course? Sigh. I wish Facebook had made this change a year ago.

Many things going forward will happen in reacts petri dish. Lots of ideas seeking to get consensus like the evolution of styles, animations, native performance, async scheduler, easy-to-create native renderers. Vue is nice and all, but it's rather complacent, catering to old Angular-like roots and web artefacts. If you believed the hype then Vue was supposed to be the be-all-end-all of frameworks, the reality of course is quite sober: http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular...

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

#422

Post by ojr »

MikeHolman wrote: post #59
blaqkangel wrote: post #11

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

>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 exodus, React is the number one javascript framework in the job market in Boston and probably other tech hubs too

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

#423

Post by ojr »

markyuckerberg wrote: post #239

As the old saying goes, you will eventually run into someone who doesn't give a fuck who or how powerful you are. Meet your Daddy, Facebook. He is called Automattic. :-) As for people who think the exodus out of React was "imaginary" - I wish FB had actually completely dropped the ball and stayed with the old license. That would have forced Automattic to not merely drop React, but also anoint a competitor which would…

Automattic, the PHP shop? I don't think they have a great influence on what javascript framework is the most popular. The job market is trending towards React and now it will be even more so, the people who thought the patents was no big deal are now rewarded

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

#424

Post by dis-sys »

Mayzie wrote: post #374
jancsika wrote: post #214

Earlier quoted context omitted.

From https://code.facebook.com/posts/112130496157735/explaining-r... > As our business has become successful, we've become a larger target for meritless patent litigation. This type of litigation can be extremely costly in terms of both resources and attention. It would have been easy for us to stop contributing to open source, or to do what some other large companies do and only release software that isn't used in o…

Or what about Google's Golang PATENTS clause? https://golang.org/PATENTS

the one in Go basically says if you sue google for any Go related patents then they revoke the license. that patent retaliation clause is nothing different from the one used in Apache Licence Version 2. the one in react says they revoke your license when you sue facebook for any patent related matter.

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

#425

Post by SXX »

lemming wrote: post #356
arca_vorago wrote: post #324

Earlier quoted context omitted.

A common misconception is that under GPL all your code must be released to the public. This is not true. You only have to give code to the user after purchase. Now, it's true that the user could then upload your software to the public (under gpl), but many of the issues surrounding that (such as lost sales #) aren't as bad as people imagine they are, and in the foss world are generally made up for by high-maintainenc…

Do you have an example of a commercially successful GPL desktop app?

Synergy

[1] https://symless.com/synergy

[2] https://github.com/symless/synergy-core

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

#426

Post by rmc »

Bahamut wrote: post #334
arca_vorago wrote: post #275

Earlier quoted context omitted.

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…

Are you a lawyer? If not, you would be doing a disservice to anyone curious about the topic. My own company's lawyers consider the GPLv3 toxic and not allowed at all for company use in any software we create - that's enough for me.

> My own company's lawyers consider the GPLv3 toxic and not allowed at all for company use in any software we create - that's enough for me.

Isn't that often because the GPL would require you to release your source code? Which is different from possible patent problems? I can understand why companies don't want to release their source code, but at least it's clear ("release your code and you can't be sued"), right?

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

#427

Post by kimar »

irrational wrote: post #185
blaqkangel wrote: post #11

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

Yeah, we've already settled on Vue (because our lawyers forbade us from using React), but now I'm sure they would approve React. So... do we abandon our work on Vue (which so far is amazing) to switch to React since the React ecosystem is so large, or do we stay the course? Sigh. I wish Facebook had made this change a year ago.

Out of curiosity, what stage is your company at that your lawyer has an influence on your tech stack? Was this part of due diligence for fundraising?

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

#428

Post by [deleted] »

dsacco wrote: post #219
damosneeze wrote: post #37

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

Sorry, I'm confused, can you help me understand that blog post? I'm getting three messages from it: 1. We like React a lot with or without the license. 2. It's not our job to convince the world React's patent license is fine. 3. We're substantially moving away from React, including large rewrites. ...why are they moving away from React? I'm confused, do they believe using React implicitly supports it? They're already…

[deleted]

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

#429

Post by alecco »

cies wrote: 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'm astounded how everyone things MIT == Apache2. MIT doesn't protect you from patent litigation.

This is a backwards move. Facebook is very good at PR painting this as a win for users.

See http://en.swpat.org/wiki/Patent_clauses_in_software_licences...

an explanation https://opensource.stackexchange.com/a/1890

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

#430

Post by philipodonnell »

mlsarecmg wrote: post #421
irrational wrote: post #185

Earlier quoted context omitted.

Yeah, we've already settled on Vue (because our lawyers forbade us from using React), but now I'm sure they would approve React. So... do we abandon our work on Vue (which so far is amazing) to switch to React since the React ecosystem is so large, or do we stay the course? Sigh. I wish Facebook had made this change a year ago.

Many things going forward will happen in reacts petri dish. Lots of ideas seeking to get consensus like the evolution of styles, animations, native performance, async scheduler, easy-to-create native renderers. Vue is nice and all, but it's rather complacent, catering to old Angular-like roots and web artefacts. If you believed the hype then Vue was supposed to be the be-all-end-all of frameworks, the reality of cour…

The point has been made before that npm downloads are a poor measure of framework popularity because the architecture of the framework and the typical distribution channels can skew the number of npm pulls in a way unrelated to the number of projects utilizing it.
Post reply on HN