On React and WordPress
1–10 of 212 posts
Re: On React and WordPress
#2It's too bad that this particular point has become an issue with so many good open source projects. I still think that the risk, even for startups considering acquisition exits, is low (see this great post from a patent/IP attorney [1]), but the fact that it's enough to cause players like the ASF and WordPress to move away from it just means fewer players and less innovation in the ecosystem.
IANAL, but I wish the lawyers at Facebook would take one for the team and relax a bit on this (hey, more work for them, a plus!). If you're going to sue Facebook over patent infringement, you're probably going to spend a lot more on the suit itself than the eng costs rewriting a view layer.
[1] https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok...
Re: On React and WordPress
#3It's too bad that this particular point has become an issue with so many good open source projects. I still think that the risk, even for startups considering acquisition exits, is low (see this great post from a patent/IP attorney [1]), but the fact that it's enough to cause players like the ASF and WordPress to move away from it just means fewer players and less innovation in the ecosystem. IANAL, but I wish the la…
I agree that the risk of running into legal trouble with Facebook is pretty low for many companies. However, that doesn't make it feel any less dirty. It would be nice if the lawyers at Facebook would take a chill pill on this one but that will never happen. It will be interesting to see where OSS projects from Facebook go moving forward given that the noise surrounding their patent clause seems to get louder and louder.
On a side note - I'll bet WordPress get's rewritten in Vue.js
Re: On React and WordPress
#4> 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, we’ve been really happy with React.
Okay.
> …I'm here to say that the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library.
Am I the only one missing the "why"?
> …passing down to our users.
Is that the "why"? If so, what does he mean by it? Meaning: What is the "danger" that Matt says Automattic will never run into, but that WordPress users will run into?
Re: On React and WordPress
#5It's too bad that this particular point has become an issue with so many good open source projects. I still think that the risk, even for startups considering acquisition exits, is low (see this great post from a patent/IP attorney [1]), but the fact that it's enough to cause players like the ASF and WordPress to move away from it just means fewer players and less innovation in the ecosystem. IANAL, but I wish the la…
I agree that the risk of running into legal trouble with Facebook is pretty low for many companies. However, that doesn't make it feel any less dirty. It would be nice if the lawyers at Facebook would take a chill pill on this one but that will never happen. It will be interesting to see where OSS projects from Facebook go moving forward given that the noise surrounding their patent clause seems to get louder and lou…
Why not Preact? It seems the react compatibility would be very helpful when they already have such a significant investment into react.
Re: On React and WordPress
#6> 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, we’ve been really happy with React. Okay. > …I'm here to say that the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library. Am I the only one missing the "why"? > …passing down to our users. Is that the "why"? If so, what does he m…
I think when Matt says "long-term consistency with core" he also means consistency with the philosophical aspects of free software. Note that the piece starts with Facebook's reaction to the Apache Foundation's stance against using React.
If I understand correctly, the Calypso project was related to the administrative dashboard in their hosted WP offering (and other widgets that could be used in self-hosted WP.) Going forward it looks like Gutenberg is also about the code in the pages that visitors see on published sites.
Re: On React and WordPress
#7> 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, we’ve been really happy with React. Okay. > …I'm here to say that the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library. Am I the only one missing the "why"? > …passing down to our users. Is that the "why"? If so, what does he m…
It's saddling WordPress's massive user base with Facebook's patent clause – something the userbase likely won't realise they're agreeing to when they use WordPress.
Re: On React and WordPress
#8I hope they choose Elm.
Re: On React and WordPress
#9It's too bad that this particular point has become an issue with so many good open source projects. I still think that the risk, even for startups considering acquisition exits, is low (see this great post from a patent/IP attorney [1]), but the fact that it's enough to cause players like the ASF and WordPress to move away from it just means fewer players and less innovation in the ecosystem. IANAL, but I wish the la…
Matt is a copyleft zealot. Of course he'd drop React over this non-controversy. Anyone paying attention to how he views GPL would come to that conclusion.
Re: On React and WordPress
#10>> rewrite Gutenberg using a different library. It will likely delay Gutenberg at least a few weeks
I love this. How many times in my career have I heard "the rewrite will take us ". Good luck with that estimate.