7 ms·
I wonder how Facebook would feel if all the open source software they currently use incorporated the same license. I bet it would deter them from enjoying much
by jwingy 9y ago
I wonder how Facebook would feel if all the open source software they currently use incorporated the same license. I bet it would deter them from enjoying much of the code they built their business on. This stance seems pretty antithetical to the goal and spirit of open source software and I really hope it's not the beginning of other companies following suit and 'poisoning' the well.
- carussell 9y ago> how Facebook would feel if all the open source software they currently use incorporated the same license That would work incredibly well to neutralize patents, actually, and would be a huge win for free/open source software. It's surprising not to have seen anyone point out the logical conclusion of a world where every major license includes a React-like stance on patents: it's a world where no one is able to bring patent suits against anyone, because it means they are now violating the licenses of every piece of FOSS they're currently using. (I'm relying on the assumption that there's no entity that could perform an audit right now and conclude that there's not a single piece of FOSS underpinning their products/services/infrastructure.) Licenses like Apache 2.0, MPL2, etc all have a "MAD" policy wrt patents, but they all have a gaping hole in their strategy. The React license patches this hole in a really clever way--probably the cleverest thing since the GPL's invention of copyleft to hack copyright law by using it against itself. It's really disappointing to see people's sense of disdain for Facebook overpower their ability to appreciate how clever the React license is. Addendum from the last time [1] I commented: "FWIW, I don't use React, I don't want to, I'm not a Facebook employee, and in fact I think the world would be a lot better off with Facebook having less influence than they do today. But that doesn't change how weird it is to keep seeing comments like [those that frame the React terms in a negative light]". 1. https://news.ycombinator.com/item?id=14780358 https://news.ycombinator.com/item?id=14780358
- losvedir 9y agoIn fact, this is explicitly part of their reasoning, from the blog post linked to in the GitHub comment here: > We believe that if this license were widely adopted, it could actually reduce meritless litigation for all adopters, and we want to work with others to explore this possibility.
- CodeWriter23 9y agoAnd in the case of Facebook, reduce meritable litigation against them.
- jasonkostempski 9y ago> be a win for free/open source software Any project with such a license would be non-free, so I'm not sure how that would be a win for free software.
- carussell 9y ago> such a license would be non-free I'm inclined to say you're mistaken. The FSF hasn't published an analysis of the React terms, but if they did, it seems pretty much assured that they'd deem it a "free software license, but incompatible with the GPL". Recall that Apache 2.0, MPL2, and GPLv3—all free software licenses—have patent termination clauses as well, but they're comparatively weak. In fact, GPLv2 didn't have one, and this was the reason why Apache 2.0 is labeled as free but incompatible with GPLv2. The FSF's solution to this was to include it's own patent termination in the next update to the GPL, which is why Apache 2.0 and GPLv3 are compatible today. See https://www.gnu.org/licenses/license-list.html#apache2 https://www.gnu.org/licenses/license-list.html#apache2
- weinzierl 9y ago>> such a license would be non-free > I'm inclined to say you're mistaken. The FSF hasn't published an analysis of the React terms, but if they did, it seems pretty much assured that they'd deem it a "free software license, but incompatible with the GPL". Richard Stallman said it is non-free [1]: > React.js is nonfree because of its patent license restriction. [1] https://lists.gnu.org/archive/html/directory-discuss/2017-01/msg00003.html https://lists.gnu.org/archive/html/directory-discuss/2017-01...
- FloDo 9y ago> Richard Stallman said it is non-free And after actually reading it he said it's okay to use for GNU projects: https://lists.gnu.org/archive/html/directory-discuss/2017-01/msg00025.html https://lists.gnu.org/archive/html/directory-discuss/2017-01...
- 9y ago
- kuschku 9y agoThis is sadly false. This would only neutralize patents of actual companies that have something to create. The only ones left to hold patents would be patent trolls. This would just massively empower patent trolls, and harm everyone. Because patent trolls don’t have to license patents there’s no risk for them.
- SirensOfTitan 9y ago> This would only neutralize patents of actual companies that have something to create. Against each other only, right? They could still use their patents against patent trolls.
- kuschku 9y agoYes, but which patent troll actually uses anything that you can prove violates their patents? They’re basically immune.
- chrisco255 9y agoI mean, look at Samsung v Apple and Oracle v Google...it's not all trolls in the litigation game.
- carussell 9y agoSee my remark about impossible audits. Patent trolls are almost definitely relying on FOSS whether they're in the business of creating software or not.
- kijin 9y agoIf I were a patent troll, I would get a Windows computer with a slightly old version of Microsoft Office and nothing else on it. Even if the entire FOSS community decided to adopt a patent termination clause right now, it cannot retroactively apply to whatever fragments of FOSS code that has found its way into proprietary products so far. So I'm safe as long I don't install any new software until I'm done trollin'. Your idea would make sense If all the FOSS that was ever written came with a patent termination clause. But that's not the world we live in.
- hardwaresofton 9y agoSo this opinion almost swayed me, but the problem is that companies aren't scared of open source writers suing them. If you use project A that was written by one or two developers in their spare time (and they included a BSD+patents) clause, would Facebook fear being sued by them? Probably not -- but new companies that get anywhere close to what Facebook does (increasingly, that's everything these days) definitely live with the real possibility of facebook suing them. In theory the "no one is able to bring patent suits against anyone because they're violating licenses" is a good outcome (mostly the no patent suits part), but it doesn't quite stand up in practice because patent suits cost money, and bigger companies can sue you longer than you can sue them. I don't want a world where MAD is the default, because the large companies carry nukes, and I carry a peashooter. I will no longer use react on any new projects.
- foota 9y agoI agree this is hypothetical, but an organization could form for enforcing the license.
- hardwaresofton 9y agoThis is exactly what I don't want it to come to. That's just a corporate arms race, and I can promise you open source is not going to win. Instead of forming organizations to fight patent wars, just put effort towards fixing the patent problems.
- true_religion 9y ago> the problem is that companies aren't scared of open source writers suing them. They should be. Many popular open source projects are supported by a 'community' of large companies, or are invested into a widely respected foundation like Apache. Additionally, many projects that started off as simply a few developers, grow to the point that a company is founded to handle support and customization. An example of this would be Redis Labs---started by the originator of Redis. If even tiny patent trolls can be 'dangerous' to multinationals, I expect most would steer clear of declaring a patent war on the community at large. What if Postgres had a retaliatory patent clause? What if Linux did?
- paxy 9y ago> and would be a huge win for free/open source software It would be a huge win for companies with large software patent portfolios, which is the opposite of what the free software movement is about.
- carussell 9y ago> It would be a huge win for companies with large software patent portfolios This is backwards. Those are exactly the companies that would be harmed, because their hopes to be able to wield those patents offensively have been nixed.
- aseipp 9y agoCompanies like FB/AMZN/GOOG/MSFT have, effectively, unlimited engineering resources. And money. They simply smash any incoming problems into dust with brute force. Startups do not matter. Hell, few companies other than huge ones matter. "We might have to replace a 10,000 line piece of free software" is nothing to them. If they wage war against another MegaCo, nothing really changes with this license. That legal battle could be fought (and do damage) regardless, they can meaningfully litigate against each other. But the idea this changes anything when going against, say, smaller players? Because it "weakens" their ability to use their (massive) portfolio? Because Facebook might be "afraid" of losing some software if they file suit? Not really. So, here's how the real conversation will happen at MegaCo of your choice, should this play out: --- Alice: We want to sue for patent violation against XYZ Co. But we use XYZ Co's software. If we file suit, we'll have to stop using it due to the license. Some top-level guy with a three-letter title named "Joe": Okay. How big is their company and what software do we use? Alice: <MegaCo has more money than God so the only meaningful comparison is "cockroach" at best, and the software is in no way something they cannot acquire elsewhere> Joe: Okay. Assign 50 engineers to just recreate whatever stupid software of theirs we use, in-house. Or buy another version from someone more reliable. Then assign a billion dollars to legal to destroy them. Alice: Okay. --- And that's it. They're done. That strategy was all cleared up before lunch. Keep in mind of course Facebook will probably have enough money to litigate you into the ground so long that probably won't even be able to actually tell them to stop using your software, until they've already replaced it completely and also ruined you at the same time. It turns out when you have effectively unlimited engineering resources and money (to wage legal battles), things like "Use a new virtual DOM library" or "Replace RocksDB" don't matter at all. They can just do it and crush you anyway.
- cbuq 9y agoIf mutually assured destruction is your definition of peace... But what prevents everyone from becoming patent infringers in this scenario?
- Spivak 9y agoI guess the point is in this hypothetical world patents are useless because suing would trigger the destruction and this is good because the community can freely share and use the best designs. However, in such a world I don't think the courts would approve of this 'hack' and kill the enforceability of these clauses precisely because they render patents useless.
- cyphar 9y ago> However, in such a world I don't think the courts would approve of this 'hack' and kill the enforceability of these clauses precisely because they render patents useless. I believe that contracts that terminate if you sue the other party are fairly standard, and in court these licenses would be considered fairly similar to those contracts. I don't really know what a court would say, but if I sign a contract that says "I will not sue X for any patent infringement under the condition they don't sue me for patent infringement" I would be surprised if a court found that contract unenforceable. The right to file a patent suit is not a fundamental human right after all, why would signing it away not be possible? [IANAL]
- DannyBee 9y ago"it's a world where no one is able to bring patent suits against anyone, because it means they are now violating the licenses of every piece of FOSS they're currently using." It's also a world where entrenched companies can feel free to use whatever technology they want from smaller competitors without fear of lawsuit, and use it to further entrench themselves :) I'd put a lot more money on that happening than "happy fun kumbaya singing". This is among the many reasons that apache, et al chose not to use them when revving their licenses. It's totally worth reading the discussions that happened around these issues back then. As a friend said WRT to this issue: "Everything old is new again"
- carussell 9y agoSee my response to your top-level comment above. https://news.ycombinator.com/item?id=15051709 https://news.ycombinator.com/item?id=15051709
- emiliobumachar 9y ago>It's also a world where entrenched companies can feel free to use whatever technology they want from smaller competitors without fear of lawsuit, and use it to further entrench themselves I agree, but software patents are arguably bad enough that doing away with them entirely is worth the collateral. A legislative solution might exist to have the best of both worlds, but, in the absence of that, suppose there's a copyleft-analogue hacky way to undermine software patents indiscriminately without requiring an Act of Congress. (and that's not a sure thing at all, but suppose.) Wouldn't you press the button?
- JoshMnem 9y agoIf the goal were to get rid of software patents, why don't all the large tech companies just band together and lobby against allowing patents for software? (more like Europe) This looks more like a sneaky trick by Facebook.
- cyphar 9y ago> It's surprising not to have seen anyone point out the logical conclusion of a world where every major license includes a React-like stance on patents The thing is, I agree with your premise that we should always push for licenses that (in the long term) will result in a better free software world where threats such as software patents and draconian copyright are effectively neutralised. All three GPLs did this to copyright (as you noted), and Apache helped step forward on the patent front. I would love to say that the React license helped further this cause. Unfortunately I don't agree, and it's for several reasons. * This may sound like a minor point, but the React patent license only applies to Facebook's patents, and relies on Facebook retaliating. Code contributed by anyone else may not be giving you the same protection, which means that if they sue someone other than Facebook the target has no real protection. Apache and GPLv3 both tackle this problem because the copyright license is terminated if anyone sues a copyright holder (and GPLv3 even more so because it's copyleft). By only terminating the patent license, you're relying on Facebook suing the offensive party. * As with almost all patents, Facebook makes it exceptionally explicit that independent discoveries will not be protected. While this is to be expected because it's the default patent law position, it's not exactly what you want if you're going to try to sell me on this being "an ingenious, anti-patent license". * The patent license clearly favours protecting Facebook over the wider software community. The fact that suits "(i) against Facebook or any of its subsidiaries or corporate affiliates," will result in termination means that the license is incredibly asymmetric in it's protection. The problem is that the "more free" stance of extending this protection to every user of the software would be too strong of a stance for companies to take (it would mean that no company could sue any other over patents in fear of being vulnerable to Facebook's patent portfolio). Not to mention that it still wouldn't solve the patent problem, you'd need to fix my first point and make it apply to all patents by all users. And then it would be seen as an incredibly risky business decision. * By definition the patent grant cannot be used against Facebook, because of the above protections are not provided. If Facebook sues you over a patent unrelated to React, you cannot counter-sue them for any patents they may be infringing because then you'd be giving them more ammunition. This is where your comparison to the GPL falls flat for me. The GPL does protect users in this situation. I understand that these might seem like "perfect being the enemy of good", but you have to consider that Facebook's dominant position is what makes these sorts of discussions critical. Sun made some mistakes in the CDDL, and we're still living with those mistakes to this day thanks to the whole Oracle OpenSolaris fiasco (though it went better than we could've hoped). We need to be far more careful in how we evaluate software licenses, and thinking about doomsday scenarios is crucial. If Facebook became a bad actor, would this patent license be better or worse for the community than Apache 2 or GPLv3?
- Lazare 9y ago> I wonder how Facebook would feel if all the open source software they currently use incorporated the same license. I'm pretty sure they'd be thrilled. That seems to be their aim. > I bet it would deter them from enjoying much of the code they built their business on. Why? Serious question; I just don't see why Facebook would care.