WordPress Abandons React Due to Patents Clause
wptavern.com
WordPress Abandons React Due to Patents Clause
1–10 of 12 posts
Re: WordPress Abandons React Due to Patents Clause
#2Too bad about this...
Re: WordPress Abandons React Due to Patents Clause
#3Why not just use Inferno (which is MIT licensed), or Preact?
Inferno has 1:1 feature parity with React, and is significantly faster. With react-compat it can even masquerade as React entirely, allowing people to use the React docs to learn and develop with it.
Re: WordPress Abandons React Due to Patents Clause
#4Why not just use Inferno (which is MIT licensed), or Preact? Inferno has 1:1 feature parity with React, and is significantly faster. With react-compat it can even masquerade as React entirely, allowing people to use the React docs to learn and develop with it.
Inferno is awesome I'm working on a project with webmidi and inferno there is no shim for webmidi fir react native so infernos speed is key for me.
Re: WordPress Abandons React Due to Patents Clause
#5Why not just use Inferno (which is MIT licensed), or Preact? Inferno has 1:1 feature parity with React, and is significantly faster. With react-compat it can even masquerade as React entirely, allowing people to use the React docs to learn and develop with it.
Any patents that cover React are likely to describe VDom in genereal, which means there is little reason to believe those are much safer.
Re: WordPress Abandons React Due to Patents Clause
#6Why not just use Inferno (which is MIT licensed), or Preact? Inferno has 1:1 feature parity with React, and is significantly faster. With react-compat it can even masquerade as React entirely, allowing people to use the React docs to learn and develop with it.
If the issue is patents, not copyright, moving to Preact isn't going to make you any safer.
Re: WordPress Abandons React Due to Patents Clause
#7Why not just use Inferno (which is MIT licensed), or Preact? Inferno has 1:1 feature parity with React, and is significantly faster. With react-compat it can even masquerade as React entirely, allowing people to use the React docs to learn and develop with it.
If the issue is patents , not copyright, moving to Preact isn't going to make you any safer.
Then neither is any front end lib that could be violating broadly defined patents.
Re: WordPress Abandons React Due to Patents Clause
#8Anyone know which are the patents in question?
Reactjs was released in 2013. I just did a quick search for a few plausible keywords on Google Scholar, and it revealed nothing.
It would be nice if Facebook would come clean as to which of the patents that they would claim cover React.
Re: WordPress Abandons React Due to Patents Clause
#9As an aside, there's a 'try-vue' now. https://github.com/WordPress/gutenberg/tree/try/vue
Re: WordPress Abandons React Due to Patents Clause
#10Anyone know which are the patents in question? Reactjs was released in 2013. I just did a quick search for a few plausible keywords on Google Scholar, and it revealed nothing. It would be nice if Facebook would come clean as to which of the patents that they would claim cover React.
Its not just patents in React. Its patents in "any software, technology, product or service of Facebook or any of its subsidiaries or corporate affiliates"