On React and WordPress | Matt Mullenweg
Big companies like to bury unpleasant news on Fridays: A few weeks ago, Facebook announced they have decided to dig in on their patent clause addition to the React license, even after Apache had said its no longer allowed for Apache.org projects. In their words, removing the patent clause would ”increase the amount of time and money we have to spend fighting meritless lawsuits.”I’m not judging Facebook or saying they’re wrong, it’s not my place. They have decided it’s right for them it’s their work and they can decide to license it however they wish. I appreciate that they’ve made their intentions going forward clear.A few years ago, Automattic used React as the basis for the ground-up rewrite of WordPress.com we called Calypso, I believe it’s one of the larger React-based open source projects. As our general counsel wrote, we made the decision that we’d never run into the patent issue. That is still true today as it was then, and overall, weve been really happy with React. More recently, the WordPress community started to use React for Gutenberg, the largest core project we’ve taken on in many years. People’s experience with React and the size of the React community including Calypso was a factor in trying out React for Gutenberg, and that made React the new de facto standard for WordPress and the tens of thousands of plugins written for WordPress.
0 kommentarer