Yeah because small startups will totally go after Facebook. Make sense. Wow.
Startups should not use React
51–60 of 176 posts
Re: Startups should not use React
#52> If all giants agreed to open source under the “BSD + patents” scheme, cross-adoption would grind to a halt. Why? If Google released Project X under “BSD + Patents”, and Amazon really liked it, rather than adopting it and losing their right to ever sue Google for patents, they would go off and build it on their own. This seems like a reasonable argument, but it doesn't seem to have deterred several big name companie…
Developers are not lawyers, and developers and lawyers don't talk to each other all the time. I wonder how many of those companies even bothered to check the license, given how fast they have to move? I've been guilty of that as well in the past.
Re: Startups should not use React
#53Re: Startups should not use React
#54Re: Startups should not use React
#55Re: Startups should not use React
#56Earlier quoted context omitted.
If they published React under Apache v2 at one point in time, how can they later re-release under a new license and claim patent rights on it then? Since, assuming whatever patents they own covered this version of React as well...wouldn't that be considered prior art?
From what I understood, It is not a patent on React. As far as I can tell nothing about React is patented... and that is not the discussion over the past few days has been about. This whole shebang has nothing to do with React itself, or the "technology" that React uses or anything, but more about the way many FB's open source libraries are licensed, one of which is React. The license specify that you are free to use…
Correction: Without losing your license to use any patents on React. Which...
> As far as I can tell nothing about React is patented...
I agree. Which means the entire issue is a huge paper tiger; you lose your right to use something that doesn't seem to exist.
Re: Startups should not use React
#57What is the safe alternative here? I mean probably FB got patents. and Probably they have at least one that covers things React can do. Almost every framework moved to components and virtual DOM. So there is a big chance that any framework out there could infringe some of these React patents. So their either can revoke your React license when you sue them or Sue you over patent infringement if you don't use React
> revoke your React license when you sue them
Incorrect; all they can do is revoke your patent grant and then sue you for patent infringement. They can't "revoke your React license".
So the difference is, if you use React they can only sue you for patent infringement if you sue them first; if you use something else they can sue you no matter what...
...if they have a patent on React. Despite your breezy assertion, patents are public, people have looked, and none have been found.
Re: Startups should not use React
#58Earlier quoted context omitted.
If I understand that license correctly, it is not 'patents that cover react', it is 'any facebook patent, present or future'. Also as explained in the article, it is also about my patents if I have any, in case facebook tries violating them. Far wider than 'react patents'.
I understand that but here's the scenario I'm talking about: - I use React for my startup's dashboard - I sue facebook for violating my startup's patent without removing my react dashboard first Now, what patents can facebook use to counter sue me that they couldn't sue me with anyway had I not used react?
Re: Startups should not use React
#59"Look, we were going to buy you for $500million but our thorough due diligence has turned over a rather nasty stone that you probably wished we didn't look under. You know what I mean don't you? YES - we found out your dirty little secret that you're using ReactJS. Due to this, we have decided to pull the deal in favor of your competitor who uses AngularJS. What you need to understand is that although you've cornered…
If you're using angular, you're almost certainly using Typescript which contains this less extreme version of the same sort of patent clause: 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to…
Re: Startups should not use React
#60Earlier quoted context omitted.
If they published React under Apache v2 at one point in time, how can they later re-release under a new license and claim patent rights on it then? Since, assuming whatever patents they own covered this version of React as well...wouldn't that be considered prior art?
From what I understood, It is not a patent on React. As far as I can tell nothing about React is patented... and that is not the discussion over the past few days has been about. This whole shebang has nothing to do with React itself, or the "technology" that React uses or anything, but more about the way many FB's open source libraries are licensed, one of which is React. The license specify that you are free to use…
Only if something in React is patented. As I read it, only the patent license is revoked if you sue Facebook, so if nothing in React is patented then the patent license is superfluous anyway and you should have nothing to worry about.
The issue with the Apache license seems to be that the Apache license itself contains a similar patent license with a similar revocation clause (if you sue anyone, but only if you sue them over the Apache licensed software). I presume (not a lawyer) this means the licenses are incompatible, and Facebook's software can't be used in an Apache licensed product.