This post is from a low-reputation account and contains an unverified outbound link. Be cautious before clicking external links.

5 Reasons Facebook Messed Up With React.js Licensing

webmink(28)
Published in
#blog
Words
153
Reading
1 min
Listen
Play
9y

Apache banned RocksDB and React.js because of the novel license Facebook used for them. Regardless of the actual terms of the license and patent grant, Facebook messed up by inventing a novel legal instrument they thought solved everyone's problems. Facebook’s rookie mistake of inventing its own open source license is always a bad idea. There are a range of important considerations that are not about the immediate risks or the specific instance. Their license action hits pretty much all of them!

  • License approval by OSI is really important. They didn't address it.
  • Developers rely on having permission in advance. This meant they had to seek approval from counsel.
  • Open source communities demand a leval playing field for all. Facebook advantaged only themselves.
  • "Permissive" licenses rely on an implied patent grant. Facebook's action voided it.
  • They sought to play in Apache's ecosystem. Facebook ignored their way of doing things.

Read more about this at:
https://meshedinsights.com/2017/07/27/5-reasons-facebooks-react-license-was-a-mistake/

Beware falling rocks

5 Reasons Facebook Messed Up With React.js Licensing | Ecency