41–50 of 298 posts
Earlier quoted context omitted.
"We are also working on an Android implementation which we will release later"
It's taking them a long time since the announcement of the new framework at React conf. They said they would release an Android compatible version soon and still we're waiting for any updates beside the usual cliche.
The first thing I do now on each Facebook open-source reveal, is to check the PATENTS file for the toxic second paragraph, to see if they've changed it. Sadly, no. I can't imagine being able to use this at any decent-sized company with lawyers. :-( https://github.com/facebook/react-native/blob/master/PATENTS See for example the discussions at https://news.ycombinator.com/item?id=9111849 (eg. https://news.ycombinator.…
The general argument is made that there is an implicit patent license granted when an open-source license is applied to a software product, and that this explicit patent license somehow overrides the implicit patent license (despite not being part of the license itself).
I've received different advice on the matter, so YMMV. But at the Google level, I'd imagine there'd be channels to negotiate an acceptable solution to this issue…
Earlier quoted context omitted.
Apache 2.0's license clause does not have an equivalent to "The license granted hereunder will terminate, automatically and without notice, for anyone that makes any claim (including by filing any lawsuit, assertion or other action) alleging [...] that any right in any patent claim of Facebook is invalid or unenforceable."), which is the problematic part as it means that you can't even defend yourself if Facebook sue…
The Apache version is: > If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. This seems equivalent to me, i…
It seems ComponentsKit is a very specific to iOS as opposed to React.
Earlier quoted context omitted.
It's taking them a long time since the announcement of the new framework at React conf. They said they would release an Android compatible version soon and still we're waiting for any updates beside the usual cliche.
It's been about a month since the world even knew React Native existed. You consider that a long time?
'We'll release an Android version later'
A month later:
'We'll release an Android version later'
You consider this progress at least in terms of PR & communications?
Great news! One question: since FB just announced React+Parse, I wonder how's support for Parse in React Native? Or put it a better way, if I want to write an multi-platform app based on Parse, should I consider using React Native? or it's still better to developer separate apps for each platform to get the best of Parse (especially for features like push notification)?
You can `npm install parse` and run it as usual within a React Native app
I'm curious, can somebody talk about the differences between using React Native vs ComponentsKit? It seems ComponentsKit is a very specific to iOS as opposed to React. https://github.com/facebook/componentkit
My understanding is that ComponentsKit has you write your iOS apps with ObjC/Swift or whatever, but it gives you a way of structuring your apps that is similar to React.js