react-native

I think the change in licence has something to do with mobile phone licence issues, React Native had its first official release on a date that correlates to the licence addendum changes, this is the first official tagged release : https://github.com/facebook/react-native/releases/tag/v0.14.... As you can see it is dated: "10 Nov 2015" shortly after the licence was changed.

> I suggest NativeScript as an alternative that's very similar in scope but far more mature NativeScript has been around longer than React Native (at least for Android), but going by Github activity (not the greatest metric, but not aware of a better one) React Native[1] is much more active than NativeScript[2]. Some differences between Exponent and NativeScript: - Exponent supports building iOS and Android apps on macOS, Windows, and Linux. With NativeScript you need a Mac to build iOS apps. - Exponent also allows you to push updates to published apps, while publishing with NativeScript is identical to publishing regular iOS and Android apps. [1] https://github.com/facebook/react-native [2] https://github.com/NativeScript/NativeScript

Not sure if this is the right place, but I'll ask anyway. I recently reported bugs ([0], [1]) with Facebook's Fresco and React-Native about how their usage of Object.finalize() in critical places hurts GC-performance on Android/Java. I was asked to to show how getting rid Object.finalize() actually improves performance and memory-use. Apart from a simplistic profile [2], I don't really know how to show something like that. I'm still convinced it would be good if this got fixed. [0] https://github.com/facebook/fresco/issues/1363 [1] https://github.com/facebook/react-native/issues/8780 [2] https://github.com/facebook/react-native/issues/8780#issuecomment-243705273

I recently had a little feud with the developers of react-native and fresco (the Facebook image loading library) because of their extensive use of Finalizers: https://github.com/facebook/fresco/issues/1363 https://github.com/facebook/react-native/issues/8780 Apart from being unreliable, bad design, it slows GC and instantiation by orders of magnitude, which I considered important, but they did not. I added a comment about how uninstalling the Facebook app improves the battery life of a phone dramatically, that I deleted afterwards because it was too flamy. I don't expect this to get fixed ever :(.

I don't mind switching between different contexts, I frequent the terminal for git an other stuff anyway. I think it is fairly magic that one may finally develop the same code for both iOS and Android. Huge productivity win, especially using Clojurescript! I agree with the instability though, nothing for someone afraid of rumbling around in the RN source code to solve things like this https://github.com/facebook/react-native/issues/7720

let me guess, you were hoping for npm install -g react-native git clone http://github.com/facebook/react-native/android-boilerplate cd .... npm run

It's actually just a fork of React native: https://github.com/facebook/react-native/graphs/contributors https://github.com/ptmt/react-native-desktop/graphs/contribu... so very few of the 5.5k commits came from the OS X port

That's pretty cool way to structure websites: https://github.com/facebook/react-native/blob/master/website... The chain of build steps is quite complex though... but hey, if it works...

You can use React to render static websites. You get the nice component model and the speed of static content. You can take a look at the react native[1][2] website for an example. [1] http://facebook.github.io/react-native/ [2] https://github.com/facebook/react-native/blob/master/website...