6 ms·
The way I read it, it's not evil. It's a known and deliberate shortcoming of many licenses (e.g. BSD) not to include patent stuff because it makes everything u
by lucb1e 10y ago
The way I read it, it's not evil.
It's a known and deliberate shortcoming of many licenses (e.g. BSD) not to include patent stuff because it makes everything unnecessarily complex. There was recently an article about why BSD and MIT are so popular, and it's because they're concise and understandable. There is a reason WTFPL exists and some developers resort to it as a way to avoid legalese.
Facebook clearly was aware of this "shortcoming" and being a big player, they might have wanted to be nice and say "we won't sue you for patent infringement if it turns out we have a patent on something React does". Then the managers went "but what if they sue us? Patents are not only for offense but also our defense, we would weaken our defense." And so the clause of "except if you sue us first" came into being.
And now this fuss about the patent part making it not an open source license? Oh come on.
I really don't like Facebook as a company, but this bickering is silly.
- Alex3917 10y agoAlso, let's say hypothetically that Facebook does sue you for the patents covered by React. When to comes time to establish damages, the fact that Facebook is currently giving away the licenses for free can be used to argue in court that their monetary value is zero. So even if you get hit with treble damages for willful infringement, the actual impact might not be as severe as one might otherwise suspect. (IANAL, don't try this at home, etc.)
- ronjouch 10y ago> It's a known and deliberate shortcoming of many licenses (e.g. BSD) not to include patent stuff because it makes everything unnecessarily complex. There was recently an article about why BSD and MIT are so popular, and it's because they're concise and understandable. Could you (or anyone confident in their legalese) elaborate on: * Does the Apache2 license indeed solve this? (I'm asking because I read about it in the LLVM/Clang license change proposal [1]) * Why isn't the less-popular-but-still-well-established Apache2 license more widely used, then? To counter what you are saying about simplicity, don't you think patents are a common concern that should be covered by default in a license, even at some complexity cost? [1] https://news.ycombinator.com/item?id=12531887 https://news.ycombinator.com/item?id=12531887 EDIT: precisions, wording.
- tracker1 10y agoApache 2, iirc, has similar patent provisions where you lose patent protection if you bring suit to any contributors.
- philipodonnell 10y agoImportant caveat as I understand it from other comments: Apache 2 is limited only to suits about derivative works under that specific license. Facebook's is much broader because you lose patent protection if you bring suit against Facebook about anything, even patents with nothing to do with React, like hardware, and even if Facebook is intentionally violating one of your patents.
- DannyBee 10y agoThis is correct. In apache2 you only lose the right to that work, and only the patent rights, not copyright rights. So in a work with no patents, i can sue you as much as i want without fear :P
- gbuk2013 10y agoI think you should read the article again. What it argues is that the licence essentially means that you can't initiate a lawsuit against FB for infringing one of your patents (which may have nothing to do with Reaft) without losing your React licence. Now whether that bothers you or not depends on your individual circumstances and the sanity of your particular legal jurisdiction, but it certainly would be something of interest to any corporate legal team.
- dredmorbius 10y agoA sufficient cross-branching of anti-patent-suit free software licenses would tend to make patent cases very, very difficult to pull off. If the revocation clause were broader, say, invoked for any patent suit against any contributor or user of the software, even better. That might fall afoul of antitrust or similar type restrictions, a not-uncommon problem with patent pooling type measures from what I've read and been told over the years.
- tracker1 10y agoGiven that software patents probably shouldn't even be allowed, I'm okay with this. Also, it's not THAT different from the fairly popular Apache License 2.0's patent provisions.
- gbuk2013 10y agoSorry but I think you are quite mistaken regarding Apache 2.0 - that termination clause is only triggered by patent claims relating to the "work" (i.e. the derivative software) whereas the React licence appears to cover any claims made against FB. It is a big difference! I agree that software patents should not be allowed and am fortunate to live in a mostly sane jurisdiction where they are mostly not allowed but that's not the case for everyone.
- brlewis 10y agoWho said anything about software? Facebook or one of its affiliates could infringe a hardware invention and suing them for it would have the exact same implications.
- dmayle 10y agoI agree with you, but I understand the issue being raised. The way I see this, the issue breaks down three ways (not chronologically): 1) Facebook publishes open source software, that everyone is free to use under copyright law. Everyone agrees this is a good thing. 2) The copyrighted software also includes the use of patented inventions, Facebook adds a patent license to assert that there are no submarine patents (that Facebook is not using copyleft as a means to setup future patent trolling). Everyone agrees this is a good thing. 3) The patent license is worded in such a way that it sets up a sort of 'patentleft'. Facebook is asserting not only that it's patents are defensive, but that there's a license which guarantees it. This license works kind of like copyleft does, though maybe with less precision (at the organizational level). It asserts that if your organization is using patentleft inventions, then by definition, all inventions that come from your organization are derivative works. Unlike Apple's open source license, the guarantees provided by patentleft have no bearing on your rights under copyleft. Not everyone agrees this is a good thing. For patentleft, some people work in organizations that wish to split their efforts into those benefit from patentleft, from those that don't, like they currently can with copyleft. In the case of copyleft, it's a lot easier to detect infringement (does this code use copyrighted code). At the patent level, not only is it more difficult to tell, but the litigation around it is more difficult to settle. I personally think that patents and copyrights, when done right, add value to society, but that current laws aren't "done right". Further, I think that copyleft and patentleft exist because of flaws in the existing system of patents and copyrights, are made to fix them, and I fully support that. * Disclaimer * I am currently a Facebook employee, though my views don't necessarily represent those of the company. I wasn't an employee when the license was created, and I have no work involvement either in the license, or in software covered under the license. When the second/third clauses were added, I was a Google employee worried about the effects of these clauses.
- Flimm 10y agoI'm not sure I agree that this is analogous to copyleft. Copyleft says that you must license all distributed dirivitives under the same license, but it doesn't affect any other code you produce, you could still sue Facebook for infringing on your copyright in unrelated works. Whereas Facebook's new custom license only grants you permission to use and distribute React if you never sue Facebook for patent infringement, even if the patent is unrelated to React.
- appleflaxen 10y agoisn't your concern addressed by the original article? True, the BSD License does not explicitly state that the licensee receives the right to use the licensed software under the licensor’s patents. But I’ve never heard any lawyer postulate that that document does not grant a license to fully exploit the licensed software under all of the licensor’s intellectual property. Anyone who pushes that view is thinking too hard.
- RodericDay 10y agoImagine I come up with a really cool middle-out compression algorithm. I also build my online presence using React.js. If Facebook uses my algorithm without my permission, and I sue them, do I open myself to being sued for using React.js?
- EdwardMSmith 10y agoYour explicit grant to any patents that Facebook holds that may cover react is terminated. Your license to use react is not terminated (https://code.facebook.com/pages/850928938376556 https://code.facebook.com/pages/850928938376556). So, what is the practical upshot of not having the explicit grant to the patents? Can you be sued for patent infringement for using open source software that may be covered by patents owned by the majority contributor to the open source software?
- bryanlarsen 10y agoIANAL, but: Your license to React.js patents terminates. Your license to those patents was valid before you sued, so you cannot be sued for past damages. If you continue to use React.js after you sue, you then would become vulnerable. But your usage of React.js has little to do with that. Any patent that Facebook has that applies to React.js probably also applies to pretty much any other modern web framework. There are tons of Facebook patents that you're violating already, whether you use React.js or not. Patents are only useful for trolls and big companies. Any little guy trying to assert patents is going to lose big time in the counter-suit.
- mickronome 10y agoThe problem the article points out is that it is not 'what if they sue us on a patent claim regarding this piece of software' that is the problem. The problem is that if you would bring _any_ patent claim against Facebook or any of its affiliates, the license terminates at that moment. This is obviously not a problem for everyone, but a problem no less. Using software licenses to gain additional - and completely unrelated - rights is really not something I would like to see become a trend. It sounds like going back to the dark ages, feudalism and all. Give the bullies free reign, and they will take your money and beat you up. In this case you would also have to take off your underpants and sew yourself a new pair before you can even try to fight back.
- bflesch 10y agoI think that if you have the patents to actually have a case against Facebook and decide to sue them, then it is totally reasonable for them to not give you stuff for free any longer. Not sure how that is not fair, even more for large players who can objectively decide if it is worth it or not.
- erichocean 10y ago> The way I read it, it's not evil. No, it's evil, full stop. Facebook's patent policy means, in no uncertain terms: if you have a patent, they have a worldwide, royalty-free right to use it. Don't want to give them that? Well, until you remove all usage of Facebook's "open source" code, that's the situation. Note: RocksDB also has this problem, which means CockroachDB is also infected. Tread carefully. ----- Note to downvoters: No one has a problem with Apache 2-style patent-retaliation provisions. Facebook could solve this problem TODAY by switching to that. They don't because they don't want to retaliate, they want access to unrelated patents from third-parties at zero cost, with a credible threat to damage those third-parties if they want to retain their unrelated patent rights. There's literally no other reason for Facebook to demand terms beyond Apache 2 than to do what I just described. The Apache 2 license protects Facebook and third-parties and is 100% ethical. Facebook's patent position is not, for the reasons I've stated above. The community, IMO, should shun Facebook LOUDLY until they relent and stop this bullshit. ----- Update 2: It's actually worse, because Facebook tends to do this bullshit on stuff like RocksDB and React which are incorporated in other software that you use to run your business. Using a React-based dashboard widget for your ElasticSearch cluster? Good luck suing Facebook for patent-infringement, because guess what? You agreed to let them infringe by using it, even though you didn't intend to. Facebook's patent policy requires constant policing to avoid. Like I said: EVIL.
- nashashmi 10y agoIt also means that you can infringe on all Facebook patents and instigate them into suing you. Then, because they are the instigator, you can sue them based on your patent portfolio. And not lose your license for using react.
- ignasl 10y ago> Good luck suing Facebook for patent-infringement Protecting from patent lawsuits is not evil as SW patents are bullish anyway. No one except maybe some patent trolls or some other big companies will sue Facebook for patent infrigment and if they do then this is a pretty clever defence. If you really really have something really really unique invented (which is really really unlikely) then just don't use anything by Facebook.