React Native: Initial Thoughts • Hacker News Board

Re: React Native: Initial Thoughts

#11

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

tariqr wrote: post #3

"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.

The one pain point I can see coming up again and again is that the way of making something full-width isn't to specify "width:100%" but instead to use flexbox. While that makes sense to me, I've already seen quite a few people (on SO for example) tripping up on this.

For the rest of the properties I imagine anything that's really needed will be coming - many seem trivial to implement.

Re: React Native: Initial Thoughts

#12

Post by aggronn » Mon, Mar 30, 2015, 12:57 PM UTC

colinramsay wrote: post #9

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.

I agree that having this issue dominate discussion is incredibly annoying, however I have to say, Facebook needs to make this more clear. There should not be confusion about this.

Re: React Native: Initial Thoughts

#13

Post by jk5_ » Mon, Mar 30, 2015, 12:57 PM UTC

> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead.

This is located in « The Meh » section. IMHO, it should be in the « The Good ». Using the official spec instead of reinventing the wheel is always a good move.

Re: React Native: Initial Thoughts

#14

Post by ahunt09 » Mon, Mar 30, 2015, 12:57 PM UTC

colinramsay wrote: post #9

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.

The fact that large companies are making free use of this surprised me. Is it because they don't think that the seconds clause is actually enforceable? I would love to hear more on this.

Re: React Native: Initial Thoughts

#15

Post by agmcleod » Mon, Mar 30, 2015, 12:58 PM UTC

I think these are fair concerns, but it also sounds like this person comes from a more iOS native development background. Why not stick with that? I like the idea of react native as i use react more and more in the browser, and I enjoy the workflow.

Re: React Native: Initial Thoughts

#16

Post by colinramsay » Mon, Mar 30, 2015, 1:00 PM UTC

aggronn wrote: post #12

colinramsay wrote: post #9

Earlier quoted context omitted.

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.

I agree that having this issue dominate discussion is incredibly annoying, however I have to say, Facebook needs to make this more clear. There should not be confusion about this.

This, I do agree with. Like I say, I'm not bothered about this issue, but I'm sick to death of seeing the endless stream of internet warriors throwing themselves at it. A clarification blog post would help a lot.

Re: React Native: Initial Thoughts

#17

Post by thewarrior » Mon, Mar 30, 2015, 1:00 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.

Especially when its using ES6.

Re: React Native: Initial Thoughts

#18

Post by fit2rule » Mon, Mar 30, 2015, 1:00 PM UTC

fabean wrote: post #8

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.

Why? Javascript is not without its thorns and glitches. What makes it perfect for this use, in your opinion? Is it just the general "I don't like something you like" reaction - in which case, what is it that he's wrong about here?

Re: React Native: Initial Thoughts

#19

Post by edgyswingset » Mon, Mar 30, 2015, 1:01 PM UTC

agmcleod wrote: post #15

I think these are fair concerns, but it also sounds like this person comes from a more iOS native development background. Why not stick with that? I like the idea of react native as i use react more and more in the browser, and I enjoy the workflow.

> Why not stick with that?

Eventually it'll be available for Android, so that's a valid reason.

Re: React Native: Initial Thoughts

#20

Post by pestaa » Mon, Mar 30, 2015, 1:05 PM UTC

jk5_ wrote: post #13

> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. This is located in « The Meh » section. IMHO, it should be in the « The Good ». Using the official spec instead of reinventing the wheel is always a good move.

Agreed, though it must be stated flexbox is not yet a fully implemented and deployed API, and most certainly not the easiest to use (but it is not for a trivial problem anyway.)