React Native: Initial Thoughts

#1

Post by kaishin » Mon, Mar 30, 2015, 12:03 PM UTC

React Native: Initial Thoughts
unredacted.redalemeden.com

Re: React Native: Initial Thoughts

#2

Post by Kesty » Mon, Mar 30, 2015, 12:39 PM UTC

When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.

Re: React Native: Initial Thoughts

#3

Post by tariqr » Mon, Mar 30, 2015, 12:40 PM UTC

"StyleSheet is not CSS. You will be quickly disappointed if you adventure outside the few CSS-inspired properties that React Native ships with." Maybe there will be stronger overlap in the long run.

Re: React Native: Initial Thoughts

#4

Post by badlogic » Mon, Mar 30, 2015, 12:41 PM UTC

While react-native isn't for me, some of the features are really nice. Hotswap for mobile development is definitely a very nice thing to have. I do wonder how that handles app state. Is only the UI reloaded or all of the code?

Re: React Native: Initial Thoughts

#5

Post by nkozyra » Mon, Mar 30, 2015, 12:46 PM UTC

Kesty wrote: post #2

When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.

I think this is because you're interpreting it as "Javascript is bad" instead of "Javascript is bad for this purpose." I think there are plenty of places where the latter is a totally logical statement that needs no real further explanation.

Re: React Native: Initial Thoughts

#6

Post by 0x0 » Mon, Mar 30, 2015, 12:47 PM UTC

Any further thoughts on the apparently controversial PATENTS file? https://github.com/facebook/react-native/blob/master/PATENTS

Re: React Native: Initial Thoughts

#7

Post by cristianpascu » Mon, Mar 30, 2015, 12:48 PM UTC

Kesty wrote: post #2

When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.

He's pointing to JavaScript as being "bad" when the very point of ReactNative is to bring web technologies to iOS development. What did he expect?

Re: React Native: Initial Thoughts

#8

Post by fabean » Mon, Mar 30, 2015, 12:53 PM UTC

Kesty wrote: post #2

When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.

Completely agreed. After reading that I was immediate put off about the rest of the article.

Re: React Native: Initial Thoughts

#9

Post by colinramsay » Mon, Mar 30, 2015, 12:53 PM UTC

0x0 wrote: post #6

Any further thoughts on the apparently controversial PATENTS file? https://github.com/facebook/react-native/blob/master/PATENTS

It ruins every single discussion on the topic when armchair lawyers wade in. I have no doubt that we'll see commenters now provide their own opinions on this clause without having the faintest idea of what they're talking about.

If nothing else, the list of very large companies making use of React, seemingly without concern, makes me unworried about this.

Re: React Native: Initial Thoughts

#10

Post by colinramsay » Mon, Mar 30, 2015, 12:55 PM UTC

badlogic wrote: post #4

While react-native isn't for me, some of the features are really nice. Hotswap for mobile development is definitely a very nice thing to have. I do wonder how that handles app state. Is only the UI reloaded or all of the code?

At the moment I believe it's everything JS-side. It's not like webpack hot-swapping where just the component gets replaced. The one caveat is that if you've got a native module written in Obj-C obviously you'll need a full rebuild to see any changes there.