jjshammas

Can you speak a little to the review process when it comes to deciding what gets merged into RN and what gets bundled into which release? How much of it is community driven vs. Facebook driven?

While an incredible platform, there have been major flaws that, even for an open-sourced project, are surprising to see with such a huge community behind it. For example: a major iOS memory leak persisted across two releases. Android still is missing major features like a WebView even though it has already been built in the form of third-party plugins.

The general structure for React projects in general is for all styling, scripts, and templates to be encapsulated in a single file for each component. As a developer who migrated from web development to mobile, it seems foreign to keep code with mixed purposes together. To help mitigate this, we've built tools to help us separate "CSS" from "JS," and etc.

What is your argument for the single-file encapsulation that React Native favors? Does it not become difficult to manage in larger projects once templates or controllers grow?

Are there any plans to rewrite documentation in ES2015?

In your team's opinion, should React Native be written using ES5 or ES6? Documentation examples seem to vary back and forth, and it isn't clear whether there is a recommendation for one over the other, or if it is just developer preference.

Would love to see an answer to this. Especially as people are now developing solutions to download a fresh RN bundle file at runtime, allowing an app to refactors every single view and controller over the air. Apple has traditionally been a little obscure in whether or not this is permitted. Other web frameworks like Ionic haven't had any issues, but they're also not re-rendering native views.