Why I'm Not a React Native Developer

Post by bbcbasic » Wed, Sep 28, 2016, 9:43 AM UTC

jnbiche wrote: post #42

jakebasile wrote: post #24

Earlier quoted context omitted.

I used to half joke like this, but recently I've been doing some React work in ES6 with Flowtype annotations. It's actually not that bad.

Exactly. Flow even has tagged unions now, and `maybe` types. TypeScript is also a very mature solution to this problem. A true professional works with whatever language he needs to solve his/her problem, and shores up that language with the best tools available. In this case, I half agree, because I think mobile development is best done using native platforms. But if you're doing web development, JavaScript is a must…

Post by franciscop » Wed, Sep 28, 2016, 10:09 AM UTC

bbcbasic wrote: post #188

franciscop wrote: post #159

Please what kind of programmer would ever do this? if (weAreConnected === true) { this.setState({ isConnected: true }) } else { this.setState({ isConnected: false }) } That is just verbose unnecessarily: this.setState({ isConnected: weAreConnected }); And probably not so popular, but this: var color; if (this.state.isConnected) { color = 'green' } else { color = 'red' } Would be simplified often to: var color = this.…

> what kind of programmer would ever do this? An enterprise developer.

Post by qwertyuiop924 » Wed, Sep 28, 2016, 10:39 AM UTC

tempodox wrote: post #176

qwertyuiop924 wrote: post #60

Earlier quoted context omitted.

Besides, while JS's problems are very real, they're quite exaggerated. It's still a perfectly usable language, even without TS and whatnot. And unlike some languages used for app programming, an error doesn't have the potential to hand you a segfault.

> ...an error doesn't have the potential to hand you a segfault. And that is a good thing why? So you don't realise there was an error and your app runs on in a corrupted state?

Post by qwertyuiop924 » Wed, Sep 28, 2016, 10:41 AM UTC

readymade wrote: post #104

qwertyuiop924 wrote: post #99

Earlier quoted context omitted.

Ah. I originally talking about Objective-C, so I assumed that we were talking about manual memory management. Of course, ARC has its own problems... Hope anybody implementing graphs knows what they're doing, or you'll leak memory like Niagra Falls.

Objective-C also uses ARC by default, and that's been the case for several years now. In any event, avoiding retain cycles is relatively straightforward and most iOS devs I know would agree that the low memory overhead and lack of GC pauses are worth the occasional extra effort of weak references.

Post by caub » Wed, Sep 28, 2016, 10:55 AM UTC

STRML wrote: post #21

This is simply a list of things the author doesn't like about JS, very much of which is practically solved by Flow/TS and ESLint. He also makes some of the React examples quite a bit more complicated than they need to be. Declarative UI is very simple! Here's the same code, using both class and functional styles (whichever you prefer), in a much more succinct style (11 LOC vs 49): class Root extends Component { rende…