3 ms·
> There are, AFAIK, no known patents on React. Really? That's your argument? If there are no public patents today, does it mean there's none in the works? Wha
by raulk 9y ago
> There are, AFAIK, no known patents on React.
Really? That's your argument? If there are no public patents today, does it mean there's none in the works?
What tells you there won't be a patent tomorrow?
Let me ask differently. Assuming you're a software engineer, do you pick your stack based on the status quo? Or do you pick a future-proof stack, based not only in its position today, but its projection tomorrow?
What CAN happen today is not as important as what COULD happen tomorrow, based on the legal provisions you're agreeing to by adopting React.
> If this is incorrect, and Facebook actually do hold patents on React, then all of the popular alternatives almost certainly infringe on them as well. So, the worst-case scenario is no different.
This is absolutely incorrect. It depends on the content of the patent. For example, if FB filed a patent for React Mobile, it would not affect Preact and Inferno, as these frameworks do not deal with mobile rendering.
- matthewmacleod 9y agoWhat tells you there won't be a patent tomorrow? Nothing. But that applies regardless of whether I use React, or I use any other piece of software that Facebook may or may not take a patent out on in the future. Except, in the former case, I at least had a license to begin with. This is absolutely incorrect. It depends on the content of the patent. For example, if FB filed a patent for React Mobile, it would not affect Preact and Inferno, as these frameworks do not deal with mobile rendering. There is a small outside chance that Facebook might patent a particular thing that React does that no other view framework does. It's unlikely to be the case, since most frameworks accomplish the same things in the same way.