When Facebook first introduced React, the programming world welcomed it with open arms. React allows programmers to develop interactive user interfaces without the usual hassle of coding everything from scratch. Simply design views for each state of your application and React will do the heavy lifting.

WordPress was among the many who switched to React. The latest version of WordPress.com relies heavily on React for its UI smoothness. A recent announcement from Automattic, the company behind WordPress, suggests that the company may be dropping the React library soon.

A Complete Library

There are reasons why React from Facebook is so popular. Those who are pursuing software development masters degree from reputable universities such as Maryville University are getting to know React as a handy UI library to use, while programmers working as software developers are using the library widely.

The support from programmers and programs such as online masters in software development was just the beginning. React quickly gained traction for being backed by Facebook’s own development team. Everything just worked; React even makes debugging your software a lot easier.

It wasn’t a surprise that WordPress Calypso was developed using React as one its main components. The latest iteration of WordPress.com felt lighter and more fluid in many ways, thanks to the interactive UI components provided by the library.

Patent Confusion

A recent change in Facebook’s attitude towards the patent clause covering React was the reason why Automattic decided to take a step back. WordPress’ Matt Mullenweg confirmed that React was used as a major library in the development of Calypso. Matt even confirmed that his team has been using React as part of the Gutenberg core project, WordPress’ next big thing.

That change in Facebook’s attitude was first spotted when the Apache Software Foundation added the Facebook BSD+Patents License to the list of ASF’s Category X. The official quote from the list says:

The Facebook BSD+Patents license includes a specification of a PATENTS file that passes along risk to downstream consumers of our software imbalanced in favor of the licensor, not the licensee, thereby violating our Apache legal policy of being a universal donor. The terms of Facebook BSD+Patents license are not a subset of those found in the ALv2, and they cannot be sublicensed as ALv2.

Facebook has since issued an explanation, stating that it wasn’t the company’s intention to disrespect intellectual properties. The open-source world, however, remains skeptical.

A Trojan Horse

“I think Facebook’s clause is actually clearer than many other approaches companies could take, and Facebook has been one of the better open source contributors out there,” according to Matt in a statement. Many in the open-source community agree with him, stating that the patent licensing approach is a Trojan horse into the community.

Facebook can effectively revoke the patent license of a React user if that user files for a copyright claim for a product developed using React. This gives Facebook the power to file a claim against the React user, making the use of React a double-edged sword for the user.

If you are studying for your MSSD online, you will be very aware of the potential ramifications this news will have for software developers.

Leave a Reply