eliperkins
[1]: https://github.com/facebook/relay/pull/2293
[2]: https://github.com/relay-tools/relay-compiler-language-types...
[ReactiveCocoaLayout](https://github.com/ReactiveCocoa/ReactiveCocoaLayout) is a good example of how much work it takes to get close to this pattern, but the view lifecycle as a whole (adding and removing subviews, layout passes, etc.) makes it hard.
From what I understand React-Native does this for you natively under-the-hood, but using JS as an implementation detail.
I really don't think that anyone is advocating for JS being the "better language", but rather one that has a framework (read: React.js) being used in practice which will work with native view as well.
This blog post summed it up perfectly for me: https://joshaber.github.io/2015/01/30/why-react-native-matte...
Congrats on the launch Marin! Been following the repo for a few months now, I'm really digging the design.
I don't think you ALWAYS have to run on your device. Emulators are much faster at launching and getting to it. I use the emulator for a majority of quick fixes, layout changes, API debugging, etc. I move over to the device when things are nearing a point where I need to test real-world things.
Using the emulator is fine, just be sure to test on the device before you deploy.