Live data from Hacker News

Explaining React's license

code.facebook.com

361–370 of 622 posts

Re: Explaining React's license

#361
post #173

Earlier quoted context omitted.

If React really is covered by patents Facebook has then Preact is likely infringing on them since it does the same things in similar ways. And Preact doesn't come with a patent grant from Facebook at all.

We learned from Java and Google that you can't patent and API. It's not forked from React it's an alternative.

The case was about whether or not you can copyright an API.

Re: Explaining React's license

#362

I love love love love love react as a technology, but this is just awful. I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop. I personally feel like such a fool for not taking all this seriously before the ASF gave me a wakeup call. React is a trojan horse into the open source community that Facebook purposely and maliciously stee…

Well, I planned to learn more about React, but reading now this convinced me to learn Vue.js instead. It's under MIT license developed by a single person in addition to community's contribution. This link is rather interesting https://vuejs.org/v2/guide/comparison.html#React

I made the same decision about 1-2 months ago for the same reason, and after scaffolding my project from the CLI, creating some components, and adding additional pieces I needed (vue-router, vuex, dev server proxying to my backend, etc.), Vue has been an absolute pleasure to work with.

Re: Explaining React's license

#363

I love love love love love react as a technology, but this is just awful. I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop. I personally feel like such a fool for not taking all this seriously before the ASF gave me a wakeup call. React is a trojan horse into the open source community that Facebook purposely and maliciously stee…

Here's a list of companies using React:

- Microsoft - Uber - Yahoo Mail - Dropbox - Airbnb - Netflix - NY Times

If they're ok with the license, you probably shouldn't worry too much. Basically, if you don't own any patents or if your company is smaller than any of the above, you should be ok.

Re: Explaining React's license

#364
post #346

Earlier quoted context omitted.

I think we read a different FAQ, or I'm misreading your link. The FAQ says that if Facebook sues _you_ for patent infringement and you counter sue for patent infringement that they won't revoke your license, but I don't see anything that answers the parent comment's concern.

> Does termination of the additional patent grant in the Facebook BSD+Patents license cause the copyright license to also terminate? > No. In short, if you get into a patent dispute with them, your license to use React does not terminate . So when someone says "if you sue you will lose your rights to use react" this is wrong. My rights to use React come from the BSD license, not from the patent grant.

Exactly. You'll be using the React code under the BSD license but without any patent grants.

Re: Explaining React's license

#365

I love love love love love react as a technology, but this is just awful. I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop. I personally feel like such a fool for not taking all this seriously before the ASF gave me a wakeup call. React is a trojan horse into the open source community that Facebook purposely and maliciously stee…

Agreed and there is no reason to still stick with react when alternatives like vuejs and angular are available. Its not that great anyways when compared to angular 2/4. There are too many concepts to be mastered and it soon become overwhelming. I tried learning react but dropped it after spending a week when I still could not understand routing. Sense of cohesiveness between different concepts is missing. I believe s…

Angular does not come with a patent grant at all. Vue most likely is infringing on FB patents anyway. So what is the win exactly?

Re: Explaining React's license

#366

Earlier quoted context omitted.

What's the difference between say the PATENTS file/grant in these Facebook projects and the PATENTS file/grant in Go which Kubernetes is written in? Not being inflammatory, genuinely interested as a user of both Go and React...

Not a lawyer, but as I understand it: The Go and Kubernetes patent licenses terminate if you file litigation specifically regarding those projects-- if you sue anyone for violating some garbage collector patent in Go, you lose the patent licenses Go granted. Facebook's patent license terminates if you sue Facebook, subsidiaries, or "any party relating to the Software" for any patent infringement. It doesn't have to b…

Thanks, very interesting difference.

Google's grant protects (or tries to protect) specific tech, Facebook's grant protects (or tries to protect) as an umbrella, the organisation.

Well - can't comment on how effective it will be as a disincentive to sue, but I do feel at the same time if it does succeed in that goal it will almost certainly act equally as a negative factor in adoption; because it's my opinion that this is creating a soft-walled garden around Facebook open source tech.

Re: Explaining React's license

#367
post #365

Earlier quoted context omitted.

Agreed and there is no reason to still stick with react when alternatives like vuejs and angular are available. Its not that great anyways when compared to angular 2/4. There are too many concepts to be mastered and it soon become overwhelming. I tried learning react but dropped it after spending a week when I still could not understand routing. Sense of cohesiveness between different concepts is missing. I believe s…

Angular does not come with a patent grant at all. Vue most likely is infringing on FB patents anyway. So what is the win exactly?

Angular 2 is MIT licensed. Why you need a patent grant anyways?

Re: Explaining React's license

#368

I love love love love love react as a technology, but this is just awful. I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop. I personally feel like such a fool for not taking all this seriously before the ASF gave me a wakeup call. React is a trojan horse into the open source community that Facebook purposely and maliciously stee…

> We should be able to just use it, because it's open and that's what open means.

You can. What's stopping you?

Re: Explaining React's license

#369
post #309

Earlier quoted context omitted.

Not in templates.

You need to use the Angular Language Service extension for vs code, it works perfectly giving you full type completion and error checking in templates https://github.com/angular/vscode-ng-language-service

Thanks for sharing this.

Re: Explaining React's license

#370
post #138

Earlier quoted context omitted.

https://github.com/kevinflo/react-open at least to play around with for my own purposes. I forget what the state of things even was back in .11

You should probably steer clear of trademark infringement too. I was thinking something like free-dom myself.

That's probably the most American-sounding package name I've ever heard
Post reply on HN