This is a nit pick, but isn't his "Ambiguous curly braces" example actually breaking due to automatic semicolon insertion?
return {{a: 4}}
Isn't valid anyways. ESLint easily flags it as an error.
Why I'm Not a React Native Developer
11–20 of 318 posts
Re: Why I'm Not a React Native Developer
#12tldr; Author doesn't like writing in javascript and fears that Facebook may some day decide to stop supporting React Native.
Ariel also doesn't like this clause in the React license: The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate directly or indirectly, or take a direct financial interest in, any Patent Assertion: (i) against Facebook or any of its subsidiaries or corporate affiliates, (ii) against any party if such Patent Asserti…
That's in all of the React licenses.
Re: Why I'm Not a React Native Developer
#13Earlier quoted context omitted.
Ariel also doesn't like this clause in the React license: The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate directly or indirectly, or take a direct financial interest in, any Patent Assertion: (i) against Facebook or any of its subsidiaries or corporate affiliates, (ii) against any party if such Patent Asserti…
That's in all of the React licenses.
Thanks, I updated my original comment.
Re: Why I'm Not a React Native Developer
#14You could have just said "I don't like Javascript" and ended the post there.
I feel like this is some sort of signaling, a la 'no true programmer uses javascript, because types!'.
Re: Why I'm Not a React Native Developer
#15Is anyone using TypeScript with React Native? I'd be interested to see how easy that is to integrate.
In that case it would probably make more sense to just use NativeScript instead of React Native.
Re: Why I'm Not a React Native Developer
#16Author says the bad outweigh the good, but we haven't fully evaluated the good.
So, question for people who use React Native - how long does it take to go from [100% front end developer familiar with React] ...to [writing solid native apps] with React Native? And how much platform-specific knowledge outside of RN do you need to absorb in order to do this well?
Re: Why I'm Not a React Native Developer
#17Is anyone using TypeScript with React Native? I'd be interested to see how easy that is to integrate.
In that case it would probably make more sense to just use NativeScript instead of React Native. https://www.nativescript.org/
NativeScript doesn't have tight integration with React, and I don't really want to build that layer myself.
Re: Why I'm Not a React Native Developer
#18Unless I'm wrong, the only listed alternatives are both paid and closed source. Xamarin (requires VS Pro) or Appcelerate (requires $480-$1200/year/developer).
I believe Xamarin is now free post the MS acquisition with various parts and pieces even becoming open source:
Re: Why I'm Not a React Native Developer
#19Unless I'm wrong, the only listed alternatives are both paid and closed source. Xamarin (requires VS Pro) or Appcelerate (requires $480-$1200/year/developer).
Most of the Appcelerator community i'm in touch with use the free Titanium builds instead of paying for an Appcelerator license: http://builds.appcelerator.com.s3.amazonaws.com/index.html#m...
Titanium has always been a pretty advanced product however ever since Appcelerator introduced it's licensing/arrow stuff, Titanium (and Alloy) uptake seems to have fallen off a cliff.