OK, I have no proof that this is actually true, but it is a fun thought experiment / conspiracy theory. Here me out.
I am pretty sure this change will be extremely well received by everybody using React.
It will also ensure that the majority of React users will switch to React 16 (the first version under the MIT license) because their BSD + patents license is widely mistrusted and / or disliked.
I for one like to think that this change was triggered by the shots that Matt Mullenweg fired in his post “On WordPress and React” a few days ago. I re-read his post a couple of times because I found some of the statements he made very interesting. At first glance the post reads like “OK WordPress just ditched React no big dizzle” but after re-reading it I realized that Matt just deprived React of a quantum leap in growth. Wow. Let’s go through the interesting points:
Big companies like to bury unpleasant news on Fridays
This statement is in context of Facebook’s post about sticking with the BSD + patents license after the Apache Foundation put their license on the black list.
Right in the beginning of his article he accuses Facebook of shady behavior.
I’m not judging Facebook or saying they’re wrong, it’s not my place.
This is hilarious. Translation: “I am judging Facebook and I am saying they are wrong.”
We had a many-thousand word announcement talking about how great React is and how we’re officially adopting it for WordPress, and encouraging plugins to do the same. I’ve been sitting on that post, hoping that the patent issue would be resolved in a way we were comfortable passing down to our users.
Now for the squeeze.
Squeeze even harder:
Core WordPress updates go out to over a quarter of all websites, having them all inherit the patents clause isn’t something I’m comfortable with.
Translation: “For realz Facebook?!?!? You don’t want your Framework to be used by over 25% of all websites on the internet with a snap of a finger!?!? Maybe y’allz want to think about that a little bit?”
Now for the kill:
But we have a lot of problems to tackle, and convincing the world that Facebook’s patent clause is fine isn’t ours to take on. It’s their fight.
Translation: “We don’t need all your drama. You’re on your own.”
We’ll look for something with most of the benefits of React, but without the baggage of a patents clause that’s confusing and threatening to many people.
Translation: “React is not indispensable and can easily be switched out with something similar, thank you.”
So good. He whacked them over the head in the nicest way possible.
It makes total sense to me that Matt’s post would make them rethink their licensing strategy. The Apache Foundation reject did not really mean a big impediment to their growth but loosing WordPress would deprive them of more massive adoption and may even mean a decline in React adoption going forward because Matt and WordPress as a project are just incredibly influential in the web development community.
Matt has already reacted to Facebook’s anouncement:
I am surprised and excited to see the news that Facebook is going to drop the patent clause that I wrote about last week. They’ve announced that with React 16 the license will just be regular MIT with no patent addition. I applaud Facebook for making this move, and I hope that patent clause use is re-examined across all their open source projects.
Matt is pleased about the change.
Particularly with Gutenberg there may be an approach that allows developers to write Gutenberg blocks (Gutenblocks) in the library of their choice including Preact, Polymer, or Vue, and now React could be an officially-supported option as well.
Looks like the WordPress team found out about this new-fangled compiler that Jason Miller of Preact-fame is working on which compiles, Web Components, VueJS components and Preact components into highly optimized Preact components. That’s awesome.
Meanwhile React 16 has been released and the license is indeed MIT.
If you have any remarks or comments I am happy to hear from you on Twitter.
To be notified about new posts subscribe to the feed or follow me on Twitter.