The license is ONLY a problem if you intend to initiate litigation against Facebook and can't swap out React (or a React-using product you rely on) with something else. Something tells me the number of companies that a) will ever be in a situation to sue Facebook over patents, b) rely on React or React-based products, c) don't already infringe upon any other Facebook patent without using React, AND d) would be severely harmed if sued over React patents, is exceedingly small.
Google, Amazon, Microsoft and Apple only fulfill conditions a and b (although React is non-vital to their businesses). Most startups only fulfill conditions b and d. In order to meet all four conditions, your company would have to be built entirely on React (or other FB open source technologies), be small enough not to be able to replace React, not infringe on any of the many other patents FB holds and yet somehow own patents FB infringes on and want to actively sue them.
Deciding against React because of the patent situation for most companies is the equivalent of worrying about someone stealing your second million before you have even made a single dollar.
1. Possibility of Automattic attacking FB with patents = 0%. (No issues here with React)
2. Possibility of FB attacking Automattic with patents (No issues here; Patent grant doesn't get revoked for countersuing).
3. Wordpress end users getting attacked by FaceBook (Again no issues here, grant doesn't get revoked for countersuing).
4. Wordpress end users planning to use software patents against FB - The guys who actually have a problem.
So basically, the FUD helped individuals/trolls/companies who want to wield software patents as a weapon; to the detriment of the wider community which sees software patents as evil.
This is just beyond ridiculous to characterize the FB patents addition as some sort of social good needed in the battle against patent litigation, like they are doing everyone a favour. The patents addition in the license is there to protect FB's interests. Words that specifically benefit the interests of a megacorp do not belong in an open source license meant to be used by everyone and anyone. It sets a terrible precedent that can be used to justify a whole range of different companies adding their own clauses, each of which that can be plausibly argued for. And all of that requires other companies to conduct legal counsel, altering which companies would be adopting WordPress - imposing a kind of decision making process and barrier that few if any in WP would or should desire. And it's not even worth it considering there are equally attractive alternatives out there.
The size of React's ecosystem, bus factor and the availability of React Native all are nice but overstated in their importance relative to alternatives and obscure the many other considerations the WP community weighs up.
Further more, React's ecosystem size conveys marginal benefits given that use of React in core would have been constrained (it's not like core devs would be tapping into many additional React-based tools for core work).
React Native has not proven itself to be as stellar and promotes lock-in. If we come to rely on additional FB-engineered architecture to such a degree WP bets its future on the decisions made by a corporate giant with goals very dissimilar to WP and with decisions that may change down the line. This idea that FB has somehow has the closest thing to the holy grail and so we must all jump aboard the FB train is a very foolish and shortsighted one in my view. WP was wise not to adopt it.