If you are in doubt, the license that could terminate is just the patent grant. The copyright license would remain in effect.
The TL;DR is: "That is just a patent license, and most OSS doesn't even include a patent license at all, so it seems weird to be super-concerned in this case in particular."
here's the issue when picking reactjs vs others (like vuejs)
Choice A. by picking reactjs I'm in a clear violation of FB patents, but I'm covered as long I don't sue FB.
Choice B. by picking others (like vuejs), I may or may not be violating FB patents, (virtualDOM has some prior art, as some people claim)
why it's so hard for people to understand that "May or Maynot" is a better choice of "definitely" violating FB patents in case I need to sue FB if they are killing my business by copying my patents.
I know that suing for patents is not best business model. But, having that weapon (even defensively) is better than not having one.
still people downvote for gray areas?
> Choice A. by picking reactjs I'm in a clear violation of FB patents
Please tell us what Facebook patents one is "violating" by using React.
your argument of where are the FB patents on react is an example of your naivety
my position all along has been, using other libs than react is LESS likely to violate FB patents, and thus gives more freedom to compete with FB. if that's your definition of load-of-crap, well, that's not my definition.
Would you believe that Apple today would use react in their products?
What would Steve Jobs say to someone who suggests using react in apple software/saas?
downvoting on HN is being abused here, just because someone is a big fan of reactjs and disagrees with me, they automatically downvote a valid opinion based on facts.
see for yourself, from react patent clause "The license granted hereunder will terminate, automatically and without notice,"
https://github.com/facebook/react/blob/master/PATENTS