> 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…
Startups should not use React
151–160 of 176 posts
Re: Startups should not use React
#152Earlier 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?
I don't understand this argument. They are the owners of the patents in question. That gives them a limited monopoly on the rights to use those patents, and can create any number of products using the patents, and offer them to you under any number of licenses. Facebook re-licensing React doesn't create prior art, any more than an inventor manufacturing a new product using a patent they own would create prior art.
Apache v2 has an patent clause which explicitly waives the rights of the licensor over the patents they might have on the licensed code. So, presumably, it doesn't matter if the current project has a patent because it was once licensed under Apache v2, and the so those patents can't really be exercised. Unless, any new additions since changing the license are patented. Since you can say the only code you've used with the current license is the diff from since it was Apache licensed.
But all of this is moot since you can't even take the risk of getting sued over a case which cannot be thrown out, because you might be bankrupt by the time the case is over.
Also the current discussion isn't just about the current codebase. It is about using any of FB's projects using this license and problems over suing FB (and its affiliates) for any patent infringement. (Oculus comes to mind because it presumably has tons of important patents)
Re: Startups should not use React
#153It truly seems non-mature businesses should stop relying on open-source with "baggage" and utilize only free software (AGPL3+) that has dual-licensing for commercial use with support as e.g. in Qt, unless you are 100% sure for your product lifecycle you won't get into direct business collision with the "baggage" author.
AGPL is too toxic to use. Fortunately, there's not much compelling software using it, so it's easy to avoid. Businesses should shun AGPL, period.
Re: Startups should not use React
#154Earlier quoted context omitted.
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.
> I wonder how many of those companies even bothered to check the license, given how fast they have to move? Airbnb, Netflix, and Dropbox? I guarantee you all of those companies have lawyers that reviewed the license.
Re: Startups should not use React
#155Earlier quoted context omitted.
That's a fair point. We really need some patent and license lawyers to weigh in on this and willing to put some skin in the game. I think Facebook should also be willing to change the license to clarify intent so they can't later use the license to do something other than what they claim they want to do: make software patents useless.
An IP lawyer has: https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok...
"Disclaimer: As with everything in law, I reserve the right to throw every word out like yesterday’s newspaper if presented with new information or a recent decision by a non-caffeinated judge. Hubris and the law make for bad bedfellows. If you have information or arguments that I didn’t consider, make them below! I will update this blog if any new information changes my opinion."
Re: Startups should not use React
#156Earlier quoted context omitted.
If Facebook's approach is so great, by introducing a legal provision in the OSS license, how come it has not been adopted by any other company except for Palantir, despite being introduced in 2014? I analysed 75+ OSS projects from 35 companies, and Facebook is practically alone. https://medium.com/@raulk/list-of-companies-and-popular-proj...
I commented elsewhere on this, but how about CDDL? IANAL but it seems to do the same thing, patent poison pill in the event of suit.
And even if you do, the revocation takes effect in 60 days, which is pretty friendly IMHO.
Re: Startups should not use React
#157FUD, FUD, FUD. Pure FUD. There are, AFAIK, no known patents on React. This means you can go ahead and sue Facebook for patent violations to your heart's content. The license they granted to you to use any of their patents applied to React (of which there are none) is terminated, and you can merrily continue using React. If this is incorrect, and Facebook actually do hold patents on React, then all of the popular alte…
> AFAIK Should I tell that to my investors? That AFA matthewmacleod on HN knows, we are good? > then all of the popular alternatives almost certainly infringe on them as well. But the lawsuit would be against those alternatives directly and not my company? I'm not sure about this, but I'm not also sure why we should be taking advice about this issue from non-experts.
But the lawsuit would be against those alternatives directly and not my company
We are explicitly talking about a situation in which you lose the right to use patented technology in React because you sue Facebook for violating your patents. But if you don’t use React, you don’t have a license to use those patents at all in the first place. You’re in no worse position than you were.
Re: Startups should not use React
#158Nerds shouldn't write opinion pieces about subject domains they don't understand. Seriously, stop this. Sometimes you just need to admit you have no idea what you're talking about and shut up. The author honestly thinks using Preact or Inferno could protect them from patent lawsuits. Oh, wait, maybe "Facebook holds any software patents on the Virtual DOM or the React APIs" so better use Vue and Cycle. Unless you actu…
Re: Startups should not use React
#159Earlier quoted context omitted.
Your argument is simply supporting my thesis. 1) I am not a lawyer, and my article simply analyses the compromises a company makes when adopting React (and other OSS projects licensed under the same terms), without going into Patent Law. Some lawyers think that the patent-related legal provisions are not enforceable anyway, but then it begs to ask the question. If they are not enforceable, why is Facebook so adamant…
> I am not a lawyer, and my article simply analyses the compromises a company makes when adopting React No, your article is literally FUD. "I don't know what their goals are with this, so let's assume the worst". What could that be? Nobody knows, so let's assume it's really bad and you don't want it. F, U and D. > I analysed 75+ projects from 35 companies (link: [1]), and none uses this license model. What's going on…
I didn't stalk you: you include a link in your HN profile to your Github page, I only clicked on it. Consider removing the link if you don't want people visiting your Github profile, and learning what you engage in.
Many of your statements are imprecise/incorrect.
1. Patent grants are good. Many licenses, including ASLv2, MPL, CDDL, not only include a patent grant, but also a “weak patent retaliation” clause. A minor reprimand if you adopt a project and then decide to sue THAT VERY SAME PROJECT for patent infringement. That’s a pretty fair deal. Some licenses like CDDL are quite relaxed, e.g. they even give you a 60 days grace period after you initiate the litigation to migrate away from the software under dispute. Others like MPL not only remove the patent grant, but also the copyright license as well — which depending on the project could be assumable.
2. Facebook could’ve done the same (simply by adopting ASLv2, like they did with RocksDB when they wanted to allow Apache Cassandra to use it), but they decided to introduce a “strong patent retaliation” clause, where they protect all of their patents by immediately revoking all current (hypothetical) or future patent grants of ALL SOFTWARE with that license (which also includes Jest, immutable.js, draft.js, Flow, Infer, etc.).
3. As I said in my second article, aside from Palantir, no other corporation has adopted Facebook’s “BSD-3 + strong patents retaliation clause” since 2014 (when it was first released) – based on my examination, which I linked to in my previous comment. Meanwhile, FB claims wide adoption of this license would decrease “meritless patent litigation”. If it were true, companies should be running towards this license model. So how do you explain that no one else (aside from Palantir) has adopted it, over the course of 3 years? Something doesn’t add up. I’m sure they will explain at some point.
4. You do seem to complain a lot about my style. But with regards to content, aside from you trying to lecture me in several areas where you make mistakes yourself, your main point seems to be that the scenarios I paint are conjecture. Well, yes. They are conjecture. You see: people need to imagine possible outcomes in order to take decisions and act accordingly. If it had already happened, it wouldn’t be a blog post, it would be news.
5. Yes, I am an ASF contributor. I use GNU, ASLv2, MIT, MPL, CDDL-licensed software, and that also makes me versed (not an expert, of course) in the licensing field. I am impartial to licenses as long as they work for me and the purpose of the software I'm building. Is there anything wrong with that? Please stop making camps in your head. There is no React vs. ASF conspiracy nor battle taking place. Everyone is entitled to have their own opinion, and to study the consequences from their own angles.
6. Large companies who have adopted React, like Amazon, Microsoft, Airbnb, etc. have enough manpower to migrate away if they need to file a patent infringement lawsuit against Facebook. For them, adopting React could be a good deal. Startups don’t tend to enjoy that amount of manpower; I have already answered this several times.
I could be wrong in many of my statements, I acknowledge that. But the truth is that the license creates legal provisions whereby the scenarios I envisioned would be possible, even if several conditions would have to align. Hence, what is left? Trust that FB won’t go after you? Goodwill statements from FB’s team? Sorry, mister, but those are worthless. Especially when there are legal terms mediating.
We could keep going on forever, but my time is finite so I’m going to close this discussion with you here. Good luck!
Edit 1: changed the order of some points for better flow. Edit 2: minor changes in PS.
P.S.: BTW - you will find that OSS developers who are affiliated to some Foundation (Mozilla, Apache, Eclipse, etc.) tend to be versed in licensing, without needing to be lawyers. Everybody can understand the terms. You only have to be a lawyer if you're going to enforce them.
Re: Startups should not use React
#160Nerds shouldn't write opinion pieces about subject domains they don't understand. Seriously, stop this. Sometimes you just need to admit you have no idea what you're talking about and shut up. The author honestly thinks using Preact or Inferno could protect them from patent lawsuits. Oh, wait, maybe "Facebook holds any software patents on the Virtual DOM or the React APIs" so better use Vue and Cycle. Unless you actu…
I didn't read the whole article, so my comment is about the PATENTS file and not the article. The situation isn't just about React. The PATENTS file is found in many repos, and it's leaking into the entire open source ecosystem due to dependencies. Those kinds of conditions should not be added to Free software licenses.