REACT USERS READ THIS: https://medium.com/@raulk/...

If they revoke, just move to preact. They have no patents to react itself, so you'd be fine. This should be changed, yes, but there isn't any reason to panic.

@iam13islucky why not steer clear of the whole thing and just use something else like angular2+

Ran very quickly away from react when I saw all this bullshit

@practiseSafeHex because many people, like myself, prefer reacts way of doing things. Angular just feels worse to me, and nothing has really got me like react has. Plus, I really think it's mostly a waste of time to worry about this for my self based on what I've read so far.

@iam13islucky i don't know if also react apis (that of course preact has) are also part of new license.

@slinkydeveloper there isn't a "new" license. It's had it for years, it just recently got called out and an organization said it wasn't a true Open license iirc.

@iam13islucky yeah but don't you think companies would be less apt to hire react devs if they read something like this? I feel like if any serious company were to read this theu would steer clear from anything react-related, that just narrows the job opportunities...fuck me I'm shook. I enjoy using preact more-so anyway, but still this is spooky👻

Search indeed for react jobs, then search for angular jobs, then search for Vue jobs. Whichever one has more is the horse to bet on. Simple as that.

It's quite simple, if you plan on seeing Facebook, don't use react, otherwise stop giving a shit about something that has no impact on your life.

I am on my second multi million dev project running react. The last one was for one of the biggest investment houses in our country, and they chose the stack.

What it simple means, and this comes from an actual patent lawyer, if you have lots of products using react, and you Sue facebook for something regarding one of them, that AND ONLY that product looses it's license to use react. It does not fuck up your hole company, you as a person do not loose the right to ever use react again.

It quite simply is, if you make something using our shit, you cannot sue us at the same time relating to that same something.

People are a bunch of hyper sensation fucking cry babies making a whole new fucking solar system out of a mole hill, crying over something that will affect 0.01% of our fucking population. Get fucking over yourselves.

Microsoft, Oracle, Mozilla, Google, they all have shit community supported running the exact same funcking license, only difference is, some idiot has made every body panic because he has fucking understanding about what's going on, and people are just believing the idiot.

Here for the comments...

Some of this is not correct, I work for an extremely large m.n.c and they are very wary of using react, and don't hire react devs.

We work with a lot of clients, who themselves are big companies, who also have no interest in react.

While the licensing works the way @RTRMS says, theres another side to it that concerns people, if you sue Facebook, you loose the right to use the tool. This puts Facebook in a position of power that companies don't like. Facebook in the past have done some less than legal things when it comes to monitoring and personal data. Companies really don't like the attitude from a company like this, saying if you sue us, get off our stack. You could spend years building a product, then something comes to light that you don't like ... and you're fucked ... either re-write the whole product in something else, or live with whatever the issue was.

Having dealt with legal issues in the past, I would be very skeptical using react, and its simply a headache I don't want

@practiseSafeHex but there are still a nice bundle of react jobs available, particularly in Texas that I was looking forward to applying for around next month. I know preact as well but I'm sort of at a cross-roads here, wondering if I should ditch them both altogether and just start investing all my time into Angular4 and maybe some time into something newer like Hyperapp(I hear it's been picking up popularity lately)....help me make a sound decision, lol please?

I dig the username by the way 😅

@KidLaser there are still companies looking for VB.net jobs, but I wouldn't choose my career based on that.

I would say first of all, no matter what, it is unlikely what ever you pick will be the only thing you ever use. You need to be prepared, or willing to have learnt react and move to angular (for example). If you limit yourself to 1 tech, you will limit your career.

That being said, feel free to pick one to start with and focus on. I can't speak for whats popular in your area, personally my stack is typically:

- Native iOS
- Node.js + express
- Angular2+
- Bootstrap 4
- Cloudant (or couchDB)

And then the others are typically project specific. This is what I picked based on easy of use, personal preference and whats popular here. You'll have to do your own research.

PS, yes step one to becoming an awesome dev is understanding and laughing at my username. You'll do well my friend ;-)

Haha nice, I guess that's a little helpful; my stack is quite similar except for the db and bootstrap(I fucking love zurb's foundation). But yeah I'm always learning new things everyday, I suppose I'll spend some extra time with Angular for a bit until I find a more desirable route. Thanks @practiseSafeHex lmao!
Hey off the top of your head, you wouldn't happen to know a preferable alternative for nginx would you?

@KidLaser I don't typically deal with anything to do with the server itself. I use Cloud Foundry with the default Node.js buildpack or the staticfile buildpack for angular. Whether running in the cloud or on local machine I have no concern whether is nginx or apache or whatever

@practiseSafeHex Hm I see, well thanks for the valid input earlier anyways. I think I feel a little bit more confident as to where I should be headed now, I appreciate the help, ++ to you good sir👍

@RTRMS Other companies don't do the same. Example: every project of Red Hat, angular, and every fucking project of open source world excluded idiots of Oracle and Facebook (I don't know Microsoft and Apple what licences uses)

@slinkydeveloper That whole damn company makes only open soruce stuff, you comparing apples and the moon here...

People don't spend their days thinking of ways to sue redhat, they do with facebook and apple and microsoft and oricle and so on.

A guy in India deleyed the relase of a patch for MS edge because he filed a BS lawsuite against them claiming they using something he created in said update, legally they cannot push that update out until such time as they have spend thousands of dollars dealing with that irritating, lying little cunt.

THey have to remove the claimed infringing code, then relase the update, after they have pathed around whatever that code was fixing/doing and then spend months, if not years dealing with that twat.

So its simply, you wnat to use our software, you cannto sue us if you think soemthing we made infringes on something you made using our software.

@RTRMS you are right, but this clause it's a two bladed knife, it can hurts facebook and the users. Why i have to use react with a (remote) chance to get into a lawsuit? The "fridge" example of the blog post it's remote, but possible! In the case you have explained this clause helps Facebook (and this company needs help?!), in the fridge example the user (in the worst case) can go in bankruptcy.

You can't restrict your license because some idiots haven't a work and doesn't know what to do during the all day.

The real fact is another one: the patents on softwares are idiots, the entire mechanism doesn't make any sense. I give you an example: do you know swagger-codegen? This is a sdk generator based on swagger/openapi specificarion. It exists since 3 years. 2 days ago a company created a patent on this mechanism of sdk generation. https://google.com/patents/...
Why the fuck people can do that?

@slinkydeveloper Yes that is the exact reason, because the american legal system is soo fucked, that any one for any reason under the god damned sun can sue you.

We have a client, that runs a massive international company, and their developers are not allowed to use OS software, why, becuase if something goes wrong, they cannot sue anyone for it.

That is how fucked the legal system is in america that a company wont use freely available, quiality OS software, simply becasue they cannot sue anyone for the mistakes of their own staff.

So ya, maybe if you a new start up, use view, but then again it is more liekly that FB will buy you out than suddenly invest billions in rnd for a completely unrelated product.

So for those of us back in the real world, when 99.9% of us will never be effected by this, we can carry on using it.

If it was really such a massive issue, everyone would of shat and pissed themselve senseless 3 years ago and react would note even remotely be as fucking popular as it is now, we would not be having this dicussion because we would all be using vue and facebook would likely of just pulled of from github and kept it as an internal tool, but as we live int he real world where this effects les than 0.01% of people, we are all using because it is fucking awesome and only those hell bent on randomly sueing people need to worry about the implications of such a clause.

And quite literally in exactly 15 days, give or take a few hours and time zone adjustments, it will have been 3 years since facebook added the patent clause to the repo, and it not only exists in React,, but react-native, jest and graphql, all massively popular tools that people are using in and outside of business, not being effected by these clauses in the slightest.