Live data from Hacker News

Facebook React.js License

elcaminolegal.com

81–90 of 203 posts

Re: Facebook React.js License

#81

React.js is basically licensed so that you cannot make anything that can compete with facebook corporation. Example: 1. You create something similar to Instagram using React. 2. It gets popular 3. Facebook sues you and takes all your reacts and reducers

No, this is a complete misunderstanding of the license.

Please read Facebook's official FAQ on this matter::

https://code.facebook.com/pages/850928938376556

>Does the additional patent grant in the Facebook BSD+Patents license terminate if I create a competing product?

>No.

Re: Facebook React.js License

#82
Unrelated to the actual content of the page.. but why does this site require 1.25Mb of javascript to load? It makes up nearly 70% of the entire page, and is responsible for almost 60% of the requests needed to render the page. Do you really need to use that much javascript just to render a blog post. Why?

Those webfonts also took multiple seconds to retrieve leaving the page essentially completely blank to visitors until their browsers finally pulled them down. It paused long enough I was wondering if HN had sent sufficient traffic to bring the site down.

Here's an output to a quick stab at loading the page using pingdom: https://tools.pingdom.com/#!/cpZuGy/http://www.elcaminolegal...

Re: Facebook React.js License

#83
post #75

Hi, Paul from the React team here. There have been lots of questions about the license+patents combo we use. Recently our legal team answered some of those questions. https://code.facebook.com/license-faq

Is there any talk within Facebook on amending this clause or moving React to a standard license? I believe it's stopping a lot of large companies (whom the patent clause could actually affect) from using React, and all other like-licensed Facebook software.

Re: Facebook React.js License

#84
post #75

Hi, Paul from the React team here. There have been lots of questions about the license+patents combo we use. Recently our legal team answered some of those questions. https://code.facebook.com/license-faq

"Does the additional patent grant in the Facebook BSD+Patents license terminate if Facebook sues me for patent infringement first, and then I respond with a patent counterclaim against Facebook."

No, unless your patent counterclaim is related to Facebook's software licensed under the Facebook BSD+Patents license.

I think this sums up everything.

Re: Facebook React.js License

#85
post #75

Hi, Paul from the React team here. There have been lots of questions about the license+patents combo we use. Recently our legal team answered some of those questions. https://code.facebook.com/license-faq

Hey Paul, why not get rid of all the legalese and make this bird free? "Do what you want, no warranty"

Re: Facebook React.js License

#86
post #83
post #75

Hi, Paul from the React team here. There have been lots of questions about the license+patents combo we use. Recently our legal team answered some of those questions. https://code.facebook.com/license-faq

Is there any talk within Facebook on amending this clause or moving React to a standard license? I believe it's stopping a lot of large companies (whom the patent clause could actually affect) from using React, and all other like-licensed Facebook software.

Just use Polymer, vue or something else without that problem :-)

Re: Facebook React.js License

#89
post #75

Hi, Paul from the React team here. There have been lots of questions about the license+patents combo we use. Recently our legal team answered some of those questions. https://code.facebook.com/license-faq

Thanks Paul. None of those answers are addressing the main critique of the article though.

Re: Facebook React.js License

#90

Earlier quoted context omitted.

I think it's a great illustration of the difference between "open source" and "free software." In this case the source is still openly published, but under certain circumstances you're no longer free to redistribute.

Personally I think it's a great illustration that even software developers lack reading skills. Open Source means this, no more, no less: https://opensource.org/osd-annotated

A license (such as Facebook's) that prevents me from redistributing a modified version could still qualify as "open source" so long as simple mirroring wasn't restricted.

> In practice, open source stands for criteria a little looser than those of free software. As far as we know, all existing released free software source code would qualify as open source. Nearly all open source software is free software, but there are exceptions. First, some open source licenses are too restrictive, so they do not qualify as free licenses. For example, “Open Watcom” is nonfree because its license does not allow making a modified version and using it privately. Fortunately, few programs use such licenses.

> Second, and more important in practice, many products containing computers check signatures on their executable programs to block users from installing different executables; only one privileged company can make executables that can run in the device or can access its full capabilities. We call these devices “tyrants”, and the practice is called “tivoization” after the product (Tivo) where we first saw it. Even if the executable is made from free source code, the users cannot run modified versions of it, so the executable is nonfree.

> The criteria for open source do not recognize this issue; they are concerned solely with the licensing of the source code. Thus, these unmodifiable executables, when made from source code such as Linux that is open source and free, are open source but not free. Many Android products contain nonfree tivoized executables of Linux.

http://www.gnu.org/philosophy/open-source-misses-the-point.h...

(Pasted the most relevant portion in case you lack reading skills.)

Post reply on HN