An in-depth critique of adopting React Native

The concerns seem to be an uncertain roadmap, potential patent problems with the license of react/react native, and having to write all code in JavaScript.

Compiling to JavaScript is not really mentioned, but dismissed more or less as follows:

To my mind, there is a generalised obstinate refusal to see JavaScript as inherently deficient and therefore needing replacement rather than polishing. The resulting proliferation of grafts and crutches is seen as signs of a vibrant ecosystem, whereas what it really shows is that the language is lacking in fundamentally important functionality.

Xamarin and Appcelerator are suggested as more stable, and likely long-lived competitors. They might be more stable, but apart from “acquired by …” and “got … in funding” no arguments are made why they will exist (and be maintained) longer.

…

So, I don’t know. I’m still interested in ClojureScript, which allows/inspires libraries like Om, and can be used with React Native. And I definitely don’t buy the “let’s write this in Swift instead” angle.

In my opinion React Native is at least an interesting idea, and it being implemented in JavaScript might not be ideal, but it doesn’t stop me from using interesting languages such as Elm or ClojureScript on top of it.