React Native: Initial Thoughts • Hacker News Board

Re: React Native: Initial Thoughts

#101

Post by woah » Mon, Mar 30, 2015, 5:20 PM UTC

ksherlock wrote: post #70

I played around with it a bit over the weekend. You can call it native, but at the same time, it's not completely native. For example, there is no UITableView support. That's one of the most common ways to present data. Hell, one of the first things I tried to do. (There is a bug report. They tried to support it but the code was ugly and didn't really play well with react-native so it was dropped). You can create a L…

I don't ever find myself using the default uitableview much, usually it will contain completely custom cells. Does their ersatz table view have any issues beyond the lack of a chevron?

Re: React Native: Initial Thoughts

#102

Post by thramp » Mon, Mar 30, 2015, 5:42 PM UTC

DennisP wrote: post #60

thramp wrote: post #38

Earlier quoted context omitted.

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.

It's even available in javascript: http://gridstylesheets.org/

I saw that, but using polyfills for layout give me pause.

Re: React Native: Initial Thoughts

#103

Post by thramp » Mon, Mar 30, 2015, 5:45 PM UTC

acdlite wrote: post #65

thramp wrote: post #38

Earlier quoted context omitted.

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 disagree, but I suppose this a matter of preference. For whatever it's worth, the React team did explore using a constraint-solver, but nixed the idea. They explain their reasoning here: https://www.youtube.com/watch?v=7rDsRXj9-cU&t=14m20s

Yeah, it is preference. I found that buying entirely into Autolayout + Storyboards makes for a really nice development experience.

And their reasoning makes sense. I totally get why they would avoid constraint-based layout.

Re: React Native: Initial Thoughts

#104

Post by thramp » Mon, Mar 30, 2015, 5:46 PM UTC

cageface wrote: post #90

thramp wrote: post #38

Earlier quoted context omitted.

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.

Not sure what I think about React Native as a whole but I wholeheartedly approve of using flexbox for layout. It's much more declarative and easier to understand. Autolayout is a fundamentally flawed approach to layout. Building layouts in AL is very tricky and debugging them is twice as tricky as writing them. And lord help you if you have to programmatically add or remove views from a layout at runtime.

> And lord help you if you have to programmatically add or remove views from a layout at runtime.

I disagree with the rest, but yeah... that's a sore point.

Re: React Native: Initial Thoughts

#105

Post by empthought » Mon, Mar 30, 2015, 6:19 PM UTC

15155 wrote: post #97

hokkos wrote: post #95

Earlier quoted context omitted.

Node modules are really, really bad compared to maven or NuGet. Most of them comprise of less than 100 lines of codes.

This is NOT a bad thing, and it's one of the things I personally love most about NPM and the node community in general.

Yes, it is a bad thing. It means your upstream dependencies are snippets instead of products.