Live data from Hacker News

Explaining React's license

code.facebook.com

601–610 of 622 posts

Re: Explaining React's license

#601
post #138

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.

Wow! that's an amazing library name? Would you mind if I ..er.. borrow it? (JK) :D

Re: Explaining React's license

#602

I 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…

That would just lead to under-utilization (if that's the right phrase for it) of power.

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

#603

Earlier 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

It's not what I believe. It's what the "data" shows. Sure you can believe the words. But it's actions that matter. And in that context "don't be evil" is comical at best.

Re: Explaining React's license

#604

Earlier 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…

Whoops - sorry, yes, this is a very good point. I'm usually good at checking my own US-centric POV but I totally forgot here.

Re: Explaining React's license

#605

Earlier 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

From someone who works with Angular everyday, on a multitude of projects... Angular feels far too heavy in comparison to React. While Angular can do the job, there's just too much bloat.

Re: Explaining React's license

#606
post #387

Earlier 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?

Just my opinion from working with them everyday. Angular is more of a monolithic beast attempting do everything, and mostly it can. React is more of a microorganism with one goal, which it excels at. For me, Angular feels heavy, especially since the introduction of NgModules. I guess the million breaking changes that occurred from AngularJs to Angular2 might have left a bit of a sour taste in mouth, regarding the framework. How can they introduce NgModules in like beta 10? Angular isn't a bad framework, but the question goes down to would you rather have one framework that try to do everything, or many frameworks that each try do their one thing. There are pros and cons to both. On an even more opinionated note, I really enjoy the syntax, and feel of React(jsx)... which something I don't get with Angular components. I'm not even gonna start on redux, but it's pretty fun when you get the hang of it. As with a lot of things in programming but each to their own.

Re: Explaining React's license

#607
post #422

Earlier 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.

The link that you provided is from May of 2016. AFAIK, Google won that case and the appeals and there are no ongoing appeals: https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google....

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

#608
post #258

Earlier 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/

looks like weex uses `flow-bin` which is a BSD+PATENTS repo:

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

#609

Earlier 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 2+ missed the mark on a few things. Most critically, they missed the mark on Components. Compared to Vue, React, Preact, Marko, etc...Angular 2 components are extremely verbose. And this a big problem, because Components are the building blocks for any UI.

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

#610
post #492

Earlier 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…

To me it's sort of a toss up between these two scenarios. Implicit grant that has never been tried in court vs explicit grant that only gets revoked if I initiate a patent war?
Post reply on HN