10 ms·
So... I guess I still don't understand what was wrong with BSD+Patents. I get that there's legal uncertainty: I can imagine some companies, especially larger o
by kelnos 9y ago
So... I guess I still don't understand what was wrong with BSD+Patents.
I get that there's legal uncertainty: I can imagine some companies, especially larger ones, not wanting to give up their patent-suit option just because one random small team in their org is using React. And barriers to adoption aren't a great idea when one of your goals is wide adoption.
Overall, though, I think making it much harder to file patent suits -- at least for software patents -- is a great thing. Facebook's (and others') implementation of it might have left something to be desired, and they're certainly a large company with a lot of resources behind them, so the power dynamic might be a bit lopsided, but...
Well, let's just say I'm a small company or individual who wants to release some open source code. Doing so under a BSD+Patents-style license gives me some protection from any big players who decide to use my software. How is this a bad thing?
I suppose I hold a pretty strong anti-patents stance, though. I'd be happy if (most?) patent protection just went away entirely.
As an aside, note that it looks like FB is going with straight MIT. So they're not even giving users of their software a patent grant at all anymore[1], and reserve the right to sue you later just for using their software, if they happen to have a patent on something in it.
[1] Yes, there are some legal opinions that the MIT license's language includes an implicit patent grant, but I don't believe that's a settled matter.
- SwellJoe 9y agoI think it's more about the complexity of licensing, patents, and the uncertainty a new license presents. Using a license that's been in use for a long time, and has the endorsement of major OSS organizations, is pretty much always more comfortable for developers. I wasn't uncomfortable enough with their licenses to rule out their projects based on the license, but I understand the folks who were. Even if my reading of the license makes me unafraid of it, there was enough uncertainty about how a court, particularly courts that have a history of siding with patent trolls, might interpret the license, for it to make some people nervous. Also, the belief that the copyrights and patents involved will always belong to a benevolent actor ignores a lot of tech history. See: SCO, Oracle, etc. for examples of a previously decent stakeholder being consumed by a more malevolent and litigious one with a different interpretation of the law and the license. facebook may be a huge, unassailable, force today...can we be certain that in ten years that'll still be true? I'd bet on it, but I also won't be shocked if something dramatic happens. Sun looked pretty unassailable through the 80s and 90s, and then they didn't. Big companies building big projects have to think about these things if they want to be responsible about the future of their projects. (Again, I agree that in this case, the fear is probably overblown. But, I get where it's coming from.)
- kelnos 9y agoBy that logic we'd never have any new licenses, because everyone would be afraid to use them. We take it on faith now that whenever a new release of the GPL comes out, we won't be afraid of it just because it's new. People had problems with GPLv3 when it came out, but those problems were about specific parts of the license, not "oh god it's new and scary and we don't know how to interpret it". And that's the GPL, a license orders of magnitude more complex than BSD+Patents. As an aside, I realized I read FB's license wrong -- it actually is even better for users of it, and specifically says that the patent termination clause only goes into effect if the user is the aggressor. If FB comes after you for a patent claim, you can counter-sue all you want without losing your license. So FB is actually doing the absolutely correct thing here.
- ploxiln 9y agoIf it's licensed MIT, the Engineers just say "it's MIT license like half of the libraries we already use" and it's a legal non-issue. If the license is not one of the standard ones already in use, and it mentions patents, suddenly legal gets involved and it's a disaster. They're very risk-adverse and no one's really sure what will happen when it gets to court. It doesn't have to make sense - after all, most software patents don't make sense, and most software patent lawsuits don't make sense. Copyright makes some sense - some entity wrote the code and has (or has not) given explicit permission for others to use it, and under common open-source licenses those terms are reasonably well understood. But patents can come out of left-field and be unrelated to the user or the producer of the code. Being aware of patents (which should not cover what you're doing or should not exist) makes punitive damages worse. Again, best to just put your head in the sand and hope the patents don't notice you. Any language about patents adds complications which no one wants to figure out.
- ballenf 9y agoAnd at small to medium-sized businesses, they don't have in-house IP attorneys and their in-house counsels (or outside lawyers on retainer) will likely punt such questions to an outside firm or IP specialist. And that will come with an unattractive price.
- ngrilly 9y agoI don't get your point about MIT licensed being a standard. The BSD license used by React is a standard too.
- guelo 9y agoUnethical developers that work at shitty companies with shitty lawyers were annoyed that they couldn't use React. That's all there is to it. I loved BSD+patent as one of the few potentially successful attacks on the awful software patents regime that we currently live under. This defeat means we are probably stuck with it for the rest of our careers.
- spenczar5 9y agoI think you have it backwards. The facebook patent license puts all the power in their hands, and none in yours: they can still sue you for violating their patents, but you can't sue them. It would be a much, much worse patent regime.
- guelo 9y agoIf BSD+patent was widely adopted it could disarm all sides equally.
- reustle 9y agoMaybe that's so but do you really think you can change the license or all open source projects from companies? That's a fantasy.
- eridius 9y agoNo, it only puts power in the hands of the big players. It might mean the big players can't sue each other, but they can absolutely sue the smaller companies. BSD + Patents only "disarms" anyone who's actually using the licensed software, and perhaps more importantly, depending on it to the extent that they can't reasonably move away if they lose the patent grant. Even if Facebook did start using OSS from some small company, they could probably just rewrite the software themselves if they want to sue the company.
- guelo 9y agoPatents offer small companies no protection in a dispute with a large company. The legal fight is too expensive.
- spenczar5 9y agoThe current state of things is that patents are stockpiled as deterrents, kind of like nuclear weapons. All of the big companies know that if they sued one another over some patent claim, the other side would retaliate, and it would be a big mess with no real winners. Facebook's patent clause disarms all their opponents, but leaves them free to attack. It's actually a wildly aggressive, offensive weapon, surprisingly - just like how nuclear missile defense is one of the more provocative technologies out there that possibly makes nuclear conflicts more probably. That's why it's totally unpalatable, at least at the big companies.
- jaredklewis 9y agoIt seems like people never get tired of not reading the PATENTS file. “Wildly aggressive?” Please. The agreement explicitly forbids Facebook from revoking your patent grant if they are the aggressor. Without the agreement (i.e. just BSD) Facebook is free to sue you for patent infringement. They add a file that says they can’t do that unless you sue them first and suddenly people are out for blood. Salem 2.0.
- slaymaker1907 9y agoOnly over the React patents. They could, however, sue you over your VR system or something but leave you little recourse due to not wanting to lose your React/other FB patent grants.
- jaredklewis 9y agoNope. The PATENTS file specifically says that if Facebook initiates patent litigation (related or unrelated to React) you can counter sue Facebook AND keep your React patent grant. "...if Facebook or any of its subsidiaries or corporate affiliates files a lawsuit alleging patent infringement against you in the first instance, and you respond by filing a patent infringement counterclaim in that lawsuit against that party that is unrelated to the Software, the license granted hereunder will not terminate under section (i) of this paragraph due to such counterclaim."
- Lazare 9y agoI think the story is this: 1. Software patents are a huge, huge, existential crisis facing our industry. 2. So huge, in fact, that nobody wants to deal with it. We can't realistically figure out if the libraries we are using are covered by patents, and given how broken issuance is, they probably are. 3. So the only practical solution is to use MIT licensed libraries, pretend there's no patent issue, and put our heads in the sand. 4. But Facebook's BSD+Patents license made us think about patents. Nobody stopped and said "can we use Angular? Are there patents on core elements of it?". But people did stop and ask that about React, because Facebook was (accidentally) making people think about patents, and the more you think about patents the more you wish you were a plumber and not a dev so all you'd have to deal with is toilets blocked with shit, and not software patents, which are much worse. 5. Now that it's under an MIT license it's just as dangerous to use React (maybe more) but we can pretend it's safe again. Notice that Wordpress's decision to switch from React (which probably led to this) was quite clear: They were not switching due to patent concerns about React, they were switching because the non-standard license was stirring up FUD and making people ask them uncomfortable questions. (We know this because they explicitly said so, and also because the leading contender for a new library was Preact, which is strictly more dangerous from a patent point of view than React under every possible circumstance, but has a license that lets your pretend everything is okay easier.)
- chrisco255 9y agoThis. I don't even want to know how many patents we're all infringing on in everything we ship. We all just sort of sweep this under the rug. No one ever does a technical/patent analysis. Is patent check part of your deployment pipeline? I highly doubt it. There's probably tens of thousands of broadly worded software patents out in the wild. The only thing that keeps the industry safe is how difficult it actually is to do that analysis because of the inherent complexity in both software and patent law.
- lukaszsamson 9y agoI have one counter example. I used to work at Samsung's R&D a few years ago and there patent analysis (and filing patents) was obligatory for every developer. They had been bitten by lawsuits a few times so they learned.
- madeofpalk 9y agoAs summed up my Dan Abramov: https://twitter.com/dan_abramov/status/911397710791667712 https://twitter.com/dan_abramov/status/911397710791667712 > With MIT nobody knows if you have those grants in the first place because there was never a court precedent. But not our hill to die on
- creatonez 9y agoThe root problem is that it's a revocable license. This arguably makes it not a free software license at all.