321–330 of 622 posts
Earlier quoted context omitted.
> 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've contributed to React before and will continue to do so. I haven't seen a single reason why not to. Just because React doesn't use your favorite license? Well this may shock you but I also use and help develop closed source software. In my view there is nothing morally wron…
> closed source That's not really the problem here. The problem is that by using React, even in a closed source context, you are potentially setting yourself up to not successfully make an IP claim against facebook, even for unrelated technologies.
Earlier quoted context omitted.
The risk behind Preact isn't the API . Remember, this is a discussion about patents , so what matters is fundamental concepts and algorithms. The most likely thing for Facebook to patent is the concept of a virtual DOM that's diffed to apply updates to the real DOM. IF they have such a patent (and apparently they don't), then any library that has a vdom implementation infringes, including Preact. Of course, if they D…
React is still unsafe because facebook can infringe on your patents and if you sue you will lose your rights to use react.
I don't want a non-standard license... It's just more complexity we don't need.
Make it LGPLv3 or something if you want a patent clause, don't invent your own.
Almost all of Facebook's "open source" code has the same PATENTS file, which makes them toxic if you can imagine a future where Facebook infringes one of your patents: https://github.com/search?p=5&q=org%3Afacebook+filename%3APA... This includes things far outside the React ecosystem: - Flow (JS type checker, like TypeScript) - prepack (JS optimizing transpiler) - a bunch of Android/iOS UI/debugging frameworks, - all…
Not being inflammatory, genuinely interested as a user of both Go and React...
Almost all of Facebook's "open source" code has the same PATENTS file, which makes them toxic if you can imagine a future where Facebook infringes one of your patents: https://github.com/search?p=5&q=org%3Afacebook+filename%3APA... This includes things far outside the React ecosystem: - Flow (JS type checker, like TypeScript) - prepack (JS optimizing transpiler) - a bunch of Android/iOS UI/debugging frameworks, - all…
> I am frustrated with software with trivially incompatible licenses. It's not a copyright license, and it's not incompatible with any other free software license. I'm frustrated with the misinformation spread about it. If this patent license/grant get's revoked, you are back to simply using the BSD license with no patent grant. I've read so many people say "you'd have to stop using react if you sued facebook", uh, n…
The patent license is indeed independent of the copyright license, but it's troubling enough that multiple legal teams (Apache and Google, at least) don't want to entangle themselves with it.
I'm doubtful that any licensing scheme can significantly drive patent reform. Lobbying and legal precedents hold that capability.
> We've been looking for ways around this and have reached out to ASF to see if we could try to work with them, but have come up empty. There's a pretty obvious solution to this: relicense React. The fact that Facebook isn't even considering that is a pretty strong indication that they "weaponized" their license on purpose. > To this point, though, we haven't done a good job of explaining the reasons behind our BSD +…
I would patiently beg everyone to employ some basic reasoning. Situation A: React is licensed under BSD + PATENTS. You sue Facebook for infringing your widget patent. Turns out Facebook has a patent for something in react. They revoke your grant and counter sue you for infringing that patent. Long legal battle ensues. Situation A: React is licensed under just BSD. You sue Facebook for infringing your widget patent. T…
Apache license includes an irrevocable patent grant.
Almost all of Facebook's "open source" code has the same PATENTS file, which makes them toxic if you can imagine a future where Facebook infringes one of your patents: https://github.com/search?p=5&q=org%3Afacebook+filename%3APA... This includes things far outside the React ecosystem: - Flow (JS type checker, like TypeScript) - prepack (JS optimizing transpiler) - a bunch of Android/iOS UI/debugging frameworks, - all…
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...
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 be related to React.