Live data from Hacker News

Startups should not use React

medium.com

161–170 of 176 posts

Re: Startups should not use React

#161
post #127
post #56

Earlier quoted context omitted.

> That means, if you use React, and you happen to own a patent for something that FB utilises, you can't sue FB without losing your React license. Correction: Without losing your license to use any patents on React. Which... > As far as I can tell nothing about React is patented... I agree. Which means the entire issue is a huge paper tiger; you lose your right to use something that doesn't seem to exist.

I wouldn't say it's entirely paper tiger though, given that it also discourage you from exercising any patent you have against Facebook, no matter how legitimate the patent is. I'm neither a native English speaker nor a lawyer to really understand the wording in the legalese, or if it only cover software patent or patents in general, but I think that clause is pretty broad.

If you have a patent against Facebook, let's face it, that patent claim is going to be bigger than React ever can be. The cost of switching out a JS framework would be well worth the benefits of taking a legitimate patent claim on FB.

Re: Startups should not use React

#162
post #116

Earlier quoted context omitted.

As a small startup, I absolutely love Facebook's React patent licensing. It gives me the advantage to use React (Native) while my bigger VC-funded competitors can't. It is like the opposite of economy of scale, haha. (PS: i have no plan to be acquired or raise a VC round or file any patent)

If you read the article again, you will notice the point about how large communities don't form with these licenses. Open source software shouldn't have any restrictions on who can use them and who can't. While this license don't specifically exclude a class of people explicitly, even you agree that big companies can't use these projects. So these projects effectively exclude hundreds of thousands of software develop…

Your bigger VC competitors probably used Preact, inferno or other vdom libraries so it's really not a great competitive edge.

Except it says that you're not serious about your startup's long term future.

Re: Startups should not use React

#163

I really like the idea behind this license. They want to see a world where software patents no longer exist. So they write a term into their licensing that makes it really difficult for people who do like software patents to use their stuff. I think I will move my projects over to a similar license. The only thing I would change would be to broaden it to invalidate if your company sued anybody over any patent. If eve…

>Facebook claims that if every company adopted a React-like license, that software patents as we know it would basically die. If you think patents shouldn't exist then why is the purpose of the license to protect a single company from patent lawsuits. Why isn't the license covering any patent lawsuits of any kind to any party like the ASL does? Why does the license only protect facebook? What if there are patents tha…

Facebook's licence is as half assed as the free Internet they wanted to bring into India and some African countries. It only benefits Facebook and comes with strings attached.

Re: Startups should not use React

#164
post #57
post #21

What is the safe alternative here? I mean probably FB got patents. and Probably they have at least one that covers things React can do. Almost every framework moved to components and virtual DOM. So there is a big chance that any framework out there could infringe some of these React patents. So their either can revoke your React license when you sue them or Sue you over patent infringement if you don't use React

You're mostly right, except: > revoke your React license when you sue them Incorrect; all they can do is revoke your patent grant and then sue you for patent infringement. They can't "revoke your React license". So the difference is, if you use React they can only sue you for patent infringement if you sue them first; if you use something else they can sue you no matter what... ...if they have a patent on React. Desp…

So other libraries can't be sued because there are no patents to be infringed?

And it doesn't matter that FB terminates the patent grant if you sue them, because there were no patents to start with?

Re: Startups should not use React

#166
post #127
post #56

Earlier quoted context omitted.

> That means, if you use React, and you happen to own a patent for something that FB utilises, you can't sue FB without losing your React license. Correction: Without losing your license to use any patents on React. Which... > As far as I can tell nothing about React is patented... I agree. Which means the entire issue is a huge paper tiger; you lose your right to use something that doesn't seem to exist.

I wouldn't say it's entirely paper tiger though, given that it also discourage you from exercising any patent you have against Facebook, no matter how legitimate the patent is. I'm neither a native English speaker nor a lawyer to really understand the wording in the legalese, or if it only cover software patent or patents in general, but I think that clause is pretty broad.

Here's the thing:

If you have a potential patent claim against Facebook (or any other large entity) you know that they will, as a matter of course, dig through their enormous stockpile of patents looking for some counter-claims to make the second you file. Given the size of that stockpile, they're probably going to end up with a sizeable stack, so you need to engage in some serious due diligence before filing to evaluate the strength of your claims and the strength of their likely claims.

All the React patent grant means is that, IF this happens, they can add any React-based patents to the pile, if any exist. I rather suspect that there are no React-based patents, but it doesn't really matter if they are, because statistically speaking, it's not going to materially change the size of the stack. (Not using React entirely also won't materially change the size of the stack; any hypothetical React patents probably apply to whatever hypothetical non-React tech you used instead.)

> it also discourage you from exercising any patent you have against Facebook

No, what discourages you from exercising a patent against Facebook is that they're Facebook, and they have vastly more money, lawyers, and patents than you do. The potential React patents are the least of your worries.

Re: Startups should not use React

#167
post #99

Earlier quoted context omitted.

> 1) which patents Facebook holds and > 2) which patents are relevant to each framework/library (i.e. React and various its alternatives) Facebook needs to come out and give us these answers. There are two scenarios: 1) They have "secret" patents, and the reason they hoard them is to use them as offense when being sued, forcing the suing party (whether "meritless" or meritful) significant monetary loss to rewrite the…

I disagree with the parent poster, but you're sort of confirming their point. There's no such thing as a "secret" patent. The very definition of a patent is that you publish the details in public, in exchange for a time-limited, exclusive right to it. If you want to try to keep something a trade secret, you don't patent it.

I am aware of that. That's why I put it in quotes. So far, nobody has found one that really pertains to React and co. So if that's the case and none exist, then go to (2), otherwise Facebook have one in their arsenal that nobody else is thinking about, and go to (1).

Re: Startups should not use React

#168
post #88

Do most software startups even have patentable technology? I'm rather curious about this. Most consumer and SaaS apps I know of are built on non-patented software so I generally question this advice. The fridge example was a case in point of how ridiculously low the odds of any company getting into patent litigation with Facebook are. To go to battle with FB you're gonna need millions and it's going to take years. Th…

It's purely anecdata but I've worked for a dozen different companies in my career. The only companies that are still around today are the companies that had patents.

I worked for a $5 billion 25 year old company that had no patents to its name (until this year). What matters is execution and distribution, above and beyond patents, especially in software.

Re: Startups should not use React

#169
post #87

Nerds 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…

pluma has contributed 2 commits to react: https://github.com/facebook/react/commits?author=pluma

This isn't highly relevant but it can be a probable cause for bias.

Re: Startups should not use React

#170
post #159
post #144

Earlier quoted context omitted.

> 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…

Quite frankly, given your tone I didn't feel like responding. 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 pate…

Fine. That you still don't address my main concern (i.e. that the premise of the article is clickbait and your entire argument about open source purity is orthogonal to it) tells me everything I needed to know.

> Patent grants are good.

So you're not upset with Facebook providing a patent grant but with the terms of that patent grant, fair enough.

> Facebook could’ve done the same

The projects using this patent grant are almost 100% sponsored by Facebook. They're not tied to any particular ecosystem or using Facebook services. If Facebook makes the use of the relevant patents contingent on you not suing them, I'm having a hard time feeling upset about it.

Yes, this isn't as permissive as Apache2 but "you get to use all my stuff as long as you don't sue me for stealing your ideas" sounds fairly benign.

> If it were true, companies should be running towards this license model.

This is literally an argument from popularity. Despite all appearances, IT can be mindnumbingly slow to adopt new ideas, especially ones involving politics. Most people don't care about patents -- heck, as can be seen from 90% of the people commenting on React's patent grant, most people don't understand patents.

In the JS ecosystem MIT and BSD are among the most popular licenses. The reason they're popular is that they're short and don't contain much legalese. Does that make them good licenses? Hell no, but it makes them appear easy to understand and simple. Adding a patent grant to that makes it "not simple". It's also something you have to do intentionally.

But that's beside the point. Let's just assume Facebook is wrong and having this be the standard wouldn't bring about world peace and the death of patents or what have you. Let's go with that. How does your assessment that this is evil and bad follow from that?

> Well, yes. They are conjecture.

Thank you. Then stop wrapping them as quality advice to trick people into reading your opinion.

> Please stop making camps in your head. There is no React vs. ASF conspiracy nor battle taking place.

You tried to dismiss my opinion by portraying me as a React fanboy. I pointed out why that is bullshit and you're throwing bricks in a glass house. Now you're accusing me of being the one who tries to make this about camps?

> Startups don’t tend to enjoy that amount of manpower; I have already answered this several times.

Your entire point is that startups shouldn't use React because bigcos might acquire them. Now you're literally arguing that bigcos don't have to worry about migrating away from React. Doesn't that seem entirely contradictory?

Sure, you could argue that bigcos will still factor in this cost into acquisitions but if they already pay that cost for their own projects it can't be so prohibitive to result in bad deals. And how do you rationalise Microsoft actively encouraging outside developers to use React to build on their platform? Surely this would make any resulting acquisition unnecessarily costly.

> Hence, what is left? Trust that FB won’t go after you?

Are you worried Facebook will go after you? Are you worried Google will go after you? Are you worried Apple will go after you? Software patents are already a minefield. You're far more likely to be sued by a non-operating entity.

A patent lawsuit can easily kill almost any startup. You seem to be obsessing over how many nukes you're going to be hit with while operating at a scale where being caught in the blast radius of even a single one would end you.

Oh, wait, this is completely irrelevant. The patent grant does not terminate when you get sued. It doesn't even terminate if you countersue. The patent grant ONLY terminates if you proactively sue Facebook or sue (or countersue) any user of React over React (including Facebook). If Facebook sues you and you countersue Facebook over your smart fridge patent, you still get to use React.

> but my time is finite

So is mine. But protecting people from unsubstantiated FUD is worth it.

> 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

Good, as every developer should be. But if your mischaracterization of how the patent grant can terminate isn't based on a lack of comprehension or absentmindedness, what am I to read into that?

PS: I meant what I said. You should have written an article entirely about the issues you have with the BSD+Patents issue from an aspect of open source purity. Without the conjecture and clickbait angle to it. I would have read that, too. I would probably have disagreed with some of it even if I would have upvoted it. But at least it would have provided the grounds for an honest discussion.

The argument is valid to be had. There's no point to dressing it up as if it were about startups.

You're not an idiot. You know very well that your article won't convince startup developers to drop React, it will only influence non-technical people who are risk-averse and see your headline without understanding any of it.

Instead of playing this game and claiming you "don't want to start a flame war" after writing an obviously inflammatory article, please salvage those ideas you buried in it and write that article properly.

Post reply on HN