News for hackers. Stuff that matters.

A comment on React 16. Parent comment

Re:React 16 by Dolores12 on Tuesday September 26, 2017 @12:53PM (#15340433)
[edited]
[ Parent | on HN ]
Re:React 16 by Godel_unicode on Tuesday September 26, 2017 @01:06PM (#15340545)
Here's the problem with that type of snark; when you're wrong it's really bad for you. You are responding to a question about react NATIVE, which still has the patent grenade (see below).

https://github.com/facebook/react-native/blob/master/PATENTS

[ Parent | on HN ]
Re:React 16 by ec109685 on Wednesday September 27, 2017 @12:27AM (#15344925)
What patents does react native utilize of facebook’s?
[ Parent | on HN ]
Re:React 16 by Godel_unicode on Thursday September 28, 2017 @03:27PM (#15360004)
Not sure, but that's not relevant to the patent grenade. It revokes your license if you're involved in ANY patent action against Facebook, regardless of that patent being used in RN or not.
[ Parent | on HN ]
Re:React 16 by ec109685 on Friday October 06, 2017 @01:40AM (#15414657)
It does not revoke your license to use RN if you sue Facebook.
[ Parent | on HN ]
Re:React 16 by seattle_spring on Tuesday September 26, 2017 @12:58PM (#15340474)
React !== React Native
[ Parent | on HN ]
Re:React 16 by ofirg on Tuesday September 26, 2017 @01:49PM (#15340975)
However React == React Native evals as true due to type conversion (in ECMAScript projects with or without a patent grant are both considered 'truthy'). Really even === is not good enough, The only reliably why to test for it right now is to put a patent claim against FB inside a try-catch.

* I am not a lawyer and this should not be taken as legal advice.

[ Parent | on HN ]
Re:React 16 by jonknee on Tuesday September 26, 2017 @01:15PM (#15340640)
Well, react-dom !== react-native. Both projects use core react.
[ Parent | on HN ]