As a startup, Should we avoid using React (reflecting on the BSD + patents license) Recently, i read the following article : If you’re a startup, you should not use React (reflecting on the BSD + patents license). The example in this article : Fridgebook Inc. For the sake of illustration, say you’re a fridge company “Fridgebook Inc.” who markets intelligent fridges. Your fridges have a screen that runs your proprietary application, and you use React for the UI. Overnight, you hear that Facebook decides to move into the fridge industry, and they’ve announced the worldwide launch of their new product: “FBfridge”, in just 1 week. In the hypothetical case that Facebook blatantly infringes some of your patents with ‘FBfridge’, what can you do? Well, you cannot sue them immediately. You’re using React on the customer-facing app, remember? If you sue them before migrating to something else (like vue.js), you will immediately lose the license grant for React, and suddenly you’re in breach yourself, fighting against a potential lawsuit for illegal use of software, from an almost-$500-billion company, all by yourself. And obviously, you don’t want to interrupt customer service. So if you want to sue them, or at least hold any leverage for doing so, you will need to find a solution to migrate away from React in record time. My question: Is the claim in that article accurate, and we have to go away from React to avoid Facebook laws ?
Adding to what Martin Bonner said: If you are a startup, and your grand plan is to be bought by a big company for a lot of money, and that big company thinks your use of React makes it risky to buy you, then you will lose out. It doesn't matter whether there is a risk, what matters is whether a potential buyer believes there is a risk. And if that is your plan, then you need to re-read Martin's answer from the point of view of a bigger company. You may not have any valuable patents, but that bigger company might. If I have an LLC with no money, then I can say "I don't care if Facebook sues me for 100 millions, I'll just let the LLC go bankrupt and start another one". If the company is worth millions or more, then the risk is much higher.
Unless you have a legally valid IP right related to the specification that statement is meaningless. When a software license is granted it is based on the copyright of the code. The copyright of the spec. just stops people from copying the spec - it does not protect the information in it. You can restrict copying of the spec. under copyright, you can make up a name for the spec (like USB or Bluetooth) and get a trademark and only allow the trademark use in limited cases(doesn’t stop implementation of the spec), or get a patent that would be necessarily infringed if something complying with the spec was created and used, sold, made, etc. or you can keep it secret and only show it to people who contractually agreed with your terms.
From what I can see on the USPTO registry, &quot;tweet&quot; is still not trademarked for the purposes you're talking about. Twitter has been working to secure that trademark, but I can't find any record of them having actually secured it. Just the same, I'd predict that using it will get you at least a cease-and-desist letter, and possibly a lawsuit. Whether you'd win that case seems to be a very open question, but that presumes you have the resources to litigate.
You can't grant or license that which is not yours. For example, the Slack terms of service say: We grant to Customer a non-sublicensable, non-transferable, non-exclusive, limited license for Customer and its Authorized Users to use the object code version of these components, but solely as necessary to use the Services and in accordance with the Contract and the User Terms. So Slack's agreement with Org A does not give A any right to let any other organization B use the software. It does not matter how A and B are related, nor whether B is nonprofit or for-profit, nor what A would be getting in exchange. If B wants to use it, they need to make their own agreement with Slack.
They certainly can make that a license term and revoke the license if you do not comply. However, revoking the license is all they can do to &quot;forbid&quot;. Or they could sue you for damages without revoking the license. That said, you are free to consult how to use their software so long as you do not hold a license so that you are not bound by the terms AND you do not break the law e.g. copyright. How to do it is up to you to figure. Maybe you could simply consult users that do have a license — on their premises and devices.
Basically, you cannot do it. You are required to include the MIT license in any derivative work. However, that holds only for the parts that you import from this other project. You can identify which parts of the final product are copied from the MIT-licensed program (and indicate "these parts are subject to the following MIT license"), and then you can do whatever you want with the remainder that you wrote. The downside of not licensing your material is that nobody can use it. To use it, people would need permission, which is what a license is. If you don't license it, you don't give permission, so people can't use it. You presumably want to subject your own contribution to different licensing conditions, so then you would state those conditions and clearly indicate what parts of the code you wrote.
By &quot;unlicensed&quot; you mean that it doesn't state a license for use (MIT, GPL, etc.)? Those licenses are just a codified bundle of terms of use that cover many many edge cases. You have in place a much simpler agreement that covers the primary situation: you using/modifying the code for your own use. It's just like borrowing a car. You will ask a friend &quot;hey, could I borrow your car for a bit?&quot; &quot;sure!&quot;. You know there's a possibility that you'll get in an accident or something weird will happen, but you think the chances of that are minimal and you would be able to work it out. If you ask a car rental company, they'll give you a full contract covering every situation that may happen. Similarly, a large company would be hesitant to borrow a car for corporate use without a legal framework surrounding it. So you will likely be in the clear if you are just using it for a small project with minimal legal/financial implications. If you plan on turning your project into a multi-billion dollar empire, you should revisit your agreement.
Yes and no. [note, the following is all written about US law. In other jurisdictions laws are, of course, different (though usually not drastically so.)] In the US there are (at least) three different bodies of law that might apply to code: copyright, patents, trade secrets. Copyright covers original expression. Anything you write is automatically, immediately protected under copyright. The copyright applies to the code itself, and anything "derived" from that code. It's up to the courts to decide exactly what "derived" means. One case that's long been viewed as a landmark in this area is Gates Rubber v. Bando Chemicals. The Court of Appeals for the tenth Circuit decision includes a section titled: "The Test for Determining Whether the Copyright of a Computer Program Has Been Infringed." Note that you can register a copyright, and that can be worthwhile, such as helping recover some damages you can't otherwise. Patents are quite different from copyrights. Where a copyright covers expression of an idea, a patent covers a specific invention. Rather than being awarded automatically, a patent has to be applied for, and awarded only after the patent office has determined that there's no relevant prior art to prevent it from being awarded. A patent, however, covers things like somebody else independently discovering/inventing what's covered by the patent. A trade secret could (at least theoretically) apply to some process or procedure embodied in the code. A trade secret mostly applies to a situation where (for example) you're trying to form an alliance with some other company, and in the process tell them things you don't tell the general public. If you've identified the fact that what you're telling them is a trade secret, and they then tell a competitor (or the general public, etc.) or more generally use that information in any way other than the originally intended purpose, it could constitute a trade secret violation. As a side-note: patents and copyright fall under federal law, so they're basically uniform nation-wide. Trade secrets mostly fall under state law, so the exact details vary by state. Absent a reason to believe otherwise, I'd guess your interest here is primarily in copyright infringement. The key here would be showing that one piece of code was derived from the other. That is, it specifically would not apply in a case where there were only a limited number of ways of doing something, so anybody who wanted to do that had to use one of those ways. Since this would not indicate actual derivation, it would not indicate copyright violation.