React Native: Initial Thoughts • Hacker News Board

Re: React Native: Initial Thoughts

#41

Post by marknutter » Mon, Mar 30, 2015, 1:34 PM UTC

bryanlarsen wrote: post #29

Component-based file structure is firmly in the "good" column for me. It makes small components much more feasible. If you're forced to split out your view, your template, your stylesheet, your controller, your model, your business logic, et cetera into separate files you are forced to keep components large. However, if you have a component-based structure, whenever you notice a very small piece of common functionali…

> If you're forced to split out your view, your template, your stylesheet, your controller, your model, your business logic, et cetera into separate files you are forced to keep components large.

Why exactly does this force you to keep your components large?

Re: React Native: Initial Thoughts

#42

Post by PSeitz » Mon, Mar 30, 2015, 1:36 PM UTC

thramp wrote: post #38

acdlite wrote: post #35

> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. Flexbox is the saner API we've all be waiting for, in my opinion. I'm curious what the author's objections to it are. That's really my problem with the whole piece — statements like this are thrown out there without much justification or explanation.

I'd much rather be writing apps using constraint-based layout, much like AutoLayout. It took me a while to grok it, but it's much simpler once you get it.

I agree, imho there isn't any decalarative and powerful way to build UIs as AutoLayout.

Re: React Native: Initial Thoughts

#43

Post by EugeneOZ » Mon, Mar 30, 2015, 1:36 PM UTC

mrcwinn wrote: post #34

lucian1900 wrote: post #25

Earlier quoted context omitted.

But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.

There's nothing objective about that statement, since it depends on what you value. If you value having a language that is supported natively by every browser, I would argue JavaScript is - subjectively - quite fantastic!

It's like use iron for any work just because it's most widely available element on the Earth.

Re: React Native: Initial Thoughts

#44

Post by EugeneOZ » Mon, Mar 30, 2015, 1:37 PM UTC

ceejayoz wrote: post #32

lucian1900 wrote: post #25

Earlier quoted context omitted.

But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.

> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.

I think you overestimate Node's popularity, compared to other languages on the server side.

Re: React Native: Initial Thoughts

#45

Post by talmand » Mon, Mar 30, 2015, 1:38 PM UTC

acdlite wrote: post #35

> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. Flexbox is the saner API we've all be waiting for, in my opinion. I'm curious what the author's objections to it are. That's really my problem with the whole piece — statements like this are thrown out there without much justification or explanation.

More like that:

There's the javascript being bad with no explanation. As if there's something bad with developing tools for the javascript adept to contribute to a platform.

Browsers already doing too much comment. What? Would this person rather the team create new tools from scratch instead of leveraging a tool that the target market for this project is already using?

Notice that the "good" parts have very little or nothing to do with web development and a good number of the "bad" items do. I believe this person is not one of people intended to make use of this tool.

Re: React Native: Initial Thoughts

#46

Post by PSeitz » Mon, Mar 30, 2015, 1:39 PM UTC

lucian1900 wrote: post #25

Kesty wrote: post #2

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

But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.

Every language hat it pros and cons. Overall we could do much worse than JavaScript.

Re: React Native: Initial Thoughts

#47

Post by EugeneOZ » Mon, Mar 30, 2015, 1:41 PM UTC

lucian1900 wrote: post #25

Kesty wrote: post #2

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

But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.

It's strange to expect something else from the JS framework, so it's a really moot point in the list.

Re: React Native: Initial Thoughts

#48

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

rickyc091 wrote: post #37

legacy2013 wrote: post #26

Why is Chrome Developer Tools meh? It's something people are familiar with and has a full debugging suite

"Chrome Dev Tools. Browsers are doing too much already." I think he's trying to convey that the browser is getting too bloated and that there should perhaps be a native app to handle the debugging.

Which is daft, because to produce a separate app specifically for debugging React Native would be a huge undertaking with zero extra benefit. Chrome's Dev Tools are best in breed (IMO) and it makes sense to leverage them.

If there were things being added to Chrome Dev Tools specifically to support React Native, that'd be different.

Re: React Native: Initial Thoughts

#49

Post by talmand » Mon, Mar 30, 2015, 1:42 PM UTC

rickyc091 wrote: post #37

legacy2013 wrote: post #26

Why is Chrome Developer Tools meh? It's something people are familiar with and has a full debugging suite

"Chrome Dev Tools. Browsers are doing too much already." I think he's trying to convey that the browser is getting too bloated and that there should perhaps be a native app to handle the debugging.

So the preference would be to install a separate tool instead of using the one I already have installed to avoid bloat?

Re: React Native: Initial Thoughts

#50

Post by bkurtz13 » Mon, Mar 30, 2015, 1:43 PM UTC

OP mentions you can enable auto refresh, instead of having to Command + R every time I assume. I couldn't find that info anywhere, does anyone know how to do that? I'm really used to that workflow now with Figwheel + Om.