Does MIT license work for Apache in this case ? If yes, they can easily switch to Preact; https://preactjs.com/
Explaining React's license
221–230 of 622 posts
Re: Explaining React's license
#222I 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
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.
Re: Explaining React's license
#223I'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.
Re: Explaining React's license
#224I wonder how Facebook would feel if all the open source software they currently use incorporated the same license. I bet it would deter them from enjoying much of the code they built their business on. This stance seems pretty antithetical to the goal and spirit of open source software and I really hope it's not the beginning of other companies following suit and 'poisoning' the well.
> how Facebook would feel if all the open source software they currently use incorporated the same license That would work incredibly well to neutralize patents, actually, and would be a huge win for free/open source software. It's surprising not to have seen anyone point out the logical conclusion of a world where every major license includes a React-like stance on patents: it's a world where no one is able to bring…
If the goal were to get rid of software patents, why don't all the large tech companies just band together and lobby against allowing patents for software? (more like Europe) This looks more like a sneaky trick by Facebook.
Re: Explaining React's license
#225Earlier quoted context omitted.
No, you lose the patent license, not the copyright license. From Facebook's blog post: > The patent grant says that if you're going to use the software we've released under it, you lose the patent license from us if you sue us for patent infringement. https://code.facebook.com/posts/112130496157735/explaining-r...
Which one has more value? A file included in the repo, written in legalese, on which Every single source code file's copyright headers point to (and the README file as well), or an ambigous blog post? Reading the file in its current form ( https://github.com/facebook/react/blob/b8ba8c83f318b84e42933... ), You lose the license to make, have made, use, sell, offer to sell, import, and otherwise transfer the [React] Sof…
You lose the license granted in the PATENTS file, but you might not lose the license granted in the LICENSE file. (IANAL, so no idea whether that's true.)
Re: Explaining React's license
#226I 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…
Agreed and there is no reason to still stick with react when alternatives like vuejs and angular are available. Its not that great anyways when compared to angular 2/4. There are too many concepts to be mastered and it soon become overwhelming. I tried learning react but dropped it after spending a week when I still could not understand routing. Sense of cohesiveness between different concepts is missing. I believe s…
React Router v4 is dead simple: https://medium.com/@pshrmn/a-simple-react-router-v4-tutorial...
It's just React components up and down.
Most of the concepts that you must learn with React have to do with understanding JavaScript. If you know JS, you know 80% of what you need to know.
Re: Explaining React's license
#227Earlier quoted context omitted.
I would patiently beg everyone to employ some basic reasoning. Situation A: React is licensed under BSD + PATENTS. You sue Facebook for infringing your widget patent. Turns out Facebook has a patent for something in react. They revoke your grant and counter sue you for infringing that patent. Long legal battle ensues. Situation A: React is licensed under just BSD. You sue Facebook for infringing your widget patent. T…
If all situations are equal, why do they need the protection anyways? This is out of step with every other comparable library / framework / whatever.
What protection? The PATENTS takes rights away from Facebook, and gives rights to grantees. Facebook is in a stronger position without it. They added it to be nice.
Without patents file:
- Facebook can sue you for any reason, including react related patent infringement
- You have no patent grant for anything in react
- You can sue Facebook for anything, including patent infringement.
With patents file:
- Facebook can sue you for any reason, except for react related patent infringement
- you have a grant for any Facebook patents related to react
- You can sue Facebook for anything, including patent infringement of any kind. If you do sue them for patent related infringement, you lose the grant above (i.e. You are in same position as if there was no PATENTS file)
Re: Explaining React's license
#228Earlier 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.
Great explanation of implications of React patent clause: https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok...
Re: Explaining React's license
#229Just as a thought experiment if every piece of software had a similar clause in their license it would mark the end of software patents. Isn't this what we actually want more of? Isn't _that_ actually the moral high ground?
If that were Facebook's goal, why wouldn't they just team up with a few other large companies and lobby for abolishing software patents in the US?
Re: Explaining React's license
#230Earlier quoted context omitted.
We learned from Java and Google that you can't patent and API. It's not forked from React it's an alternative.
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…
They would have to sue on the basis that Preact and by extension all React-compatible APIs are in violation of their patent.
This would cause mass alienation in the community for little gain, and force many previously neutral parties to align against them for attacking a completely separate project.
And for little damage as well....
If we rewrote our sites to use React coming from Backbone, JQuery and Angular... it won't be too much of a hardship to rewrite our sites to no longer use React in the future. Heck considering the 5-year churn of JS frameworks, I'm already penciling in the rise of a new framework in 2022.