Explaining React's license

Re:Explaining React's license by JoshMnem on Saturday August 19, 2017 @02:24AM (#15051990)

I'm not sure if React (and the other projects that contain the PATENTS file) will survive the backlash to this in the long run. Vue.js is rapidly climbing in popularity, and Elm is probably going to go mainstream in 2018. There are alternatives like Mithril and Ember too.

[ Parent | on HN ]

Re:Explaining React's license by delambo on Saturday August 19, 2017 @10:46AM (#15053643)

The stats don't really suggest that vue is rapidly climbing in popularity:

https://npm-stat.com/charts.html?package=react&package=vue&p...

While popularity might not have anything to do with your use case, it still means a lot in terms of ecosystem, tooling, training, support and documentation.

[ Parent | on HN ]

Re:Explaining React's license by JoshMnem on Saturday August 19, 2017 @11:51AM (#15054024)

See: https://github.com/showcases/front-end-javascript-frameworks

These things usually don't happen overnight. It will be interesting to take another look about a year from now.

[ Parent | on HN ]

Re:Explaining React's license by scarlac on Saturday August 19, 2017 @05:56AM (#15052580)

The only way I see people stop using React is if there's an example of a company being counter-sued by Facebook as a result of the license or something like that.

[ Parent | on HN ]

Re:Explaining React's license by JoshMnem on Saturday August 19, 2017 @10:11AM (#15053453)

Many companies already can't use React. The numbers will increase.

[ Parent | on HN ]

Re:Explaining React's license by eugeneionesco on Saturday August 19, 2017 @04:04AM (#15052278)

This such a non-issue and affects very small part of those that use React it won't affect the popularity at all.

[ Parent | on HN ]

Re:Explaining React's license by rockdoe on Saturday August 19, 2017 @05:10AM (#15052462)

This is true if only because sane people aren't using React exactly because of this issue.

[ Parent | on HN ]