The whole ecosystem of amazing people and companies that helped build React is jeopardized, which is such a sad waste of code, development time, late nights, and humanity! Please think of long term gains and not exploding software licenses. There's already enough pain going round in the world.
Explaining React's license
251–260 of 622 posts
Re: Explaining React's license
#252Earlier quoted context omitted.
If React really is covered by patents Facebook has then Preact is likely infringing on them since it does the same things in similar ways. And Preact doesn't come with a patent grant from Facebook at all.
We learned from Java and Google that you can't patent and API. It's not forked from React it's an alternative.
API is a matter of copyright, patents can cover the methods and techniques underneath the API, and so in a way is more general, and it's possible that Facebook patents concern Vue as well.
Re: Explaining React's license
#253I love love love love love react as a technology, but this is just awful. I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop. I personally feel like such a fool for not taking all this seriously before the ASF gave me a wakeup call. React is a trojan horse into the open source community that Facebook purposely and maliciously stee…
> I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop.
I've contributed to React before and will continue to do so. I haven't seen a single reason why not to. Just because React doesn't use your favorite license? Well this may shock you but I also use and help develop closed source software. In my view there is nothing morally wrong here. What's more, it's not even clear which morals you think I would be failing by continuing to contribute to React.
Re: Explaining React's license
#254Earlier quoted context omitted.
Well, I planned to learn more about React, but reading now this convinced me to learn Vue.js instead. It's under MIT license developed by a single person in addition to community's contribution. This link is rather interesting https://vuejs.org/v2/guide/comparison.html#React
Finishing up a project at work with Vue right now, and I gotta say it's really excellent to work with. Way more intuitive than some other frameworks out there.
But does it also provide an alternative to React Native?
Re: Explaining React's license
#255Does anyone have experience with https://preactjs.com/? Is it really the same (component wise)?
Re: Explaining React's license
#256I love love love love love react as a technology, but this is just awful. I believe any developer not on Facebook's payroll still contributing to React or React native at this point has a moral obligation to stop. I personally feel like such a fool for not taking all this seriously before the ASF gave me a wakeup call. React is a trojan horse into the open source community that Facebook purposely and maliciously stee…
Well, I planned to learn more about React, but reading now this convinced me to learn Vue.js instead. It's under MIT license developed by a single person in addition to community's contribution. This link is rather interesting https://vuejs.org/v2/guide/comparison.html#React
you've made a great choice. forget about patents: vue is a joy to use. can't say the same about react, personally.
also check out nuxt.js, a small abstraction layer on top of vue that has some opinions about file structure and also makes SSR a breeze https://nuxtjs.org/
Re: Explaining React's license
#257Earlier quoted context omitted.
The risk behind Preact isn't the API . Remember, this is a discussion about patents , so what matters is fundamental concepts and algorithms. The most likely thing for Facebook to patent is the concept of a virtual DOM that's diffed to apply updates to the real DOM. IF they have such a patent (and apparently they don't), then any library that has a vdom implementation infringes, including Preact. Of course, if they D…
I believe you are mistaken, the problem with the license, if I recall the discussion correctly was that if your company used React then they can't go on a patent lawsuit with Facebook even if the patents have zilch to do with React.
> if I recall the discussion correctly was that if your company used React then they can't go on a patent lawsuit with Facebook even if the patents have zilch to do with React.
Not at all.
Re: Explaining React's license
#258Earlier quoted context omitted.
Finishing up a project at work with Vue right now, and I gotta say it's really excellent to work with. Way more intuitive than some other frameworks out there.
But does it also provide an alternative to React Native?
yes, weex[1], which is becoming some sort of apache project. it was formerly (?) an alibaba project, not actually sure on the specifics RE: changing of hands.
Re: Explaining React's license
#259Re: Explaining React's license
#260Earlier quoted context omitted.
I believe you are mistaken, the problem with the license, if I recall the discussion correctly was that if your company used React then they can't go on a patent lawsuit with Facebook even if the patents have zilch to do with React.
Great explanation of implications of React patent clause: https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok...
No.
The implication is if you use react now you give away rights.
The same is not true for angular, vue or mithril. Some argue if you use vdom there might be issue. But at least with those you/your dev is not giving away rights willingly...
But come to think of it; That is the way fb started :/