21–30 of 212 posts
>> 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.
I hope they choose Elm.
It'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…
It is assymetric to think that the solution to this problem is not within Facebook's side.
>> 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.
We've migrated reasonably large React projects to Preact using the amazing preact-compat : https://www.npmjs.com/package/preact-compat -- it was really as simple as wiring aliases in the webpack config!
I still don't understand why Facebook changed the RocksDB license so quickly but then took a hard stance on the React license.
Earlier quoted context omitted.
We've migrated reasonably large React projects to Preact using the amazing preact-compat : https://www.npmjs.com/package/preact-compat -- it was really as simple as wiring aliases in the webpack config!
Isn't it unclear if preact violates Facebook's patents?
>> 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.
Earlier quoted context omitted.
Why not Preact? It seems the react compatibility would be very helpful when they already have such a significant investment into react.
Personally, I have a hard time imagining that any Facebook patents you use with React wouldn't also apply to Preact. Then again, I think this whole patents issue is mostly FUD. The number of companies who have to reasonably consider suing Facebook for patent infringement is small and they know who they are.
It'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.
His main concern is suddenly updating ~25% of all websites to "include" the React license.
Imagine Microsoft running a small WordPress site off in the distance somewhere that takes the Wordpress + React update. Tadaa, MS is now in theory bound by the FB patent clause.
He doesn't want to be responsible for the potential legal liability of encumbering 25% of the internet with a new license agreement.