Earlier quoted context omitted.
https://github.com/kevinflo/react-open at least to play around with for my own purposes. I forget what the state of things even was back in .11
You should probably steer clear of trademark infringement too. I was thinking something like free-dom myself.
Explaining React's license
601–610 of 622 posts
Re: Explaining React's license
#602I 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 think a good principle is to never assume malicious intent, but never tolerate an abusive position either. So, Facebook, lets assume, isn't being malicious and genuinely feels this is the right approach to deal with what they consider to be "meritless" lawsuits... but at the same time, if this response-- genuine as it may be-- gives them abusive power, don't abide it. Similar principle for politicians-- never suppo…
At most situations you might be assigning improbable risks to things. If you have a reason to believe someone is not going to abuse power, then giving them said power should be okay in real life
Edit: May I add that you're swinging from one extreme to the other. Things need not be black/white. It's a fallacy all on its own
Re: Explaining React's license
#603Earlier quoted context omitted.
FB would be happy to replace the internet with Facebook. I think we've all known this for some time now. It's not their attitude, it's their entire reason for being. It's a form of totalitarianism that we don't have a word for; that's beyond most people's imagination. It would be fitting for FB to change their motto (?) to "We're not evil either." Lol
Good joke there :) Do you believe Google also has shown intents to be totalitarian or "be evil" ? IMHO Google has handled their enormous power and popularity very well. Fair Disclaimer: I must confess I'm a google user, not affiliated to them in any other way (that I know of) though :D
Re: Explaining React's license
#604Earlier quoted context omitted.
You are correct. (For the unfamiliar, there are separate rulings because in this case, the Court of Appeals for the Federal Circuit ruled that APIs are copyrightable, then remanded back to the district court to re-try the case in light of the new decision about copyrightability, which then found that reimplementation of the API was covered under fair use.)
Only in the US. In the EU, in particular, APIs cannot be copyrighted[0]. Namely: "For the avoidance of doubt, it has to be made clear that only the expression of a computer program is protected and that ideas and principles which underlie any element of a program, including those which underlie its interfaces, are not protected by copyright under this Directive." [0] http://eur-lex.europa.eu/legal-content/EN/ALL/?uri…
Re: Explaining React's license
#605Earlier quoted context omitted.
Or there is Google's Polymer framework. In my opinion, Polymer is better than React and Vue. I could never bring myself to use React because of its liense terms.
Why not Angular? It's conspicuously missing from these discussions
Re: Explaining React's license
#606Earlier quoted context omitted.
Angular is nothing like React. It's garbage in comparison.
I'm not getting the angular hate. Would you want to explain why?
Re: Explaining React's license
#607Earlier quoted context omitted.
Sorry I've forgotten what the status was on the "are APIs copyrightable" question, i.e. the Oracle v Google fight. I'm kind of confused about what wikipedia says happened - there seem to be two final rulings one in favor of Oracle and one in favor of Google with Oracle appealing the second. Is it that APIs are copyrightable but duplicating them is (sometimes?) covered under fair use? Either way, I'd be a little hesit…
APIs are copyrightable. You can see here: http://www.zerobugsandprogramfaster.net/essays/x-1.html There is still a question on fair use. Google won the jury trial, but the appellate court is ruling in a few months, and that could change everything.
Oracle really has a way of being a big swinging legal turd, I do believe they would try anything they could. It just seems like they wouldn't wait a year to get it going.
Re: Explaining React's license
#608Earlier quoted context omitted.
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. 1. https://weex.apache.org/
https://github.com/apache/incubator-weex/blob/master/package...
not sure, but I think that means users of weex are subject to BSD+PATENTS also
Re: Explaining React's license
#609Earlier quoted context omitted.
Yeah my current gig is steering clear of react because of the patent issue but we are embracing Vue and vuex.
why is angular not even being considered? Has it suddenly become radio active that no one wants to touch it even?
Angular has other issues like the AOT compilation file sizes and the fact that certain standard language features are not supported with it. But even having to know the ins and odds of AOT vs JIT...these aren't even things you have to worry about in any of the ones I mentioned above.
I really wish the Angular team had learned the best lessons from React...but they didn't. It's definitely better than Angular 1...but it's not as good as these other alternatives.
Re: Explaining React's license
#610Earlier quoted context omitted.
> if a project's license is radioactive It's not a copyright license. It's a patent grant/license which is completely independent. This matters for several reasons, including when just saying "license", this usually means a copyright license. If this patent grant get's revoked, you are back to simply using the BSD license with no patent grant. I've read so many people say "you'd have to stop using react if you sued f…
I think you're missing the plot. Currently, there is a big philosophical debate on whether OSS licenses like the BSD include an implicit patent grant. When Facebook explicitly includes a revocable patent grant, your argument of the BSD license "with no patent grant" is self-fulfilling. But if the PATENTS file had never existed, then what you have is "a BSD license with a potentially implicit patent grant", which has…