Live data from Hacker News

Why I'm Not a React Native Developer

arielelkin.github.io

211–220 of 318 posts

Re: Why I'm Not a React Native Developer

#211
post #2

Aside from the discussion of JS and React Native, I want to highlight this: > Perhaps more importantly, your software development platforms also shape you as a software engineer. A software development platform encourages (or forces) the use of one language over another, prioritises certain architectures over others, requires using specific tools and workflows, and marries you to an entire ecosystem and its developer…

Hmm, communities become less important as languages become more widely used. When was the last time you referred to the Java community, singular?

Likewise, there's not a single JavaScript community, but there's a bunch of communities around specific tools and frameworks. As you'd expect.

But I, when interviewing, expect good developers to be capable of learning new paradigms - the fact that they know nothing but node.js and node.js's ways is irrelevant, if they are capable of learning.

The author has very low expectations compared to me. And I don't feel I've been proven wrong yet by any of the hires I said yes to.

Re: Why I'm Not a React Native Developer

#212
post #148
post #47

The most part of cons is criticising JavaScript and NOT React Native. I know how JS works, and I LOVE IT. The only part of the post that I liked is when he talks about the license, all the rest is just bullshit from a person who don't like JS.

It's not bullshit if it's a valid consideration when you are trying to build an app on say iOS and weighting it against say Swift. How many times does this need to be said? It depends on what you are trying to do and what you want.

"What if you forget to put break in-between your cases in a switch statement. They will leak."

This man, my friend, is an idiot.

Re: Why I'm Not a React Native Developer

#213
post #44

I evaluated React Native for a project and decided to go with NativeScript instead for a number of reasons: 1. RN releases a new version every 2 weeks breaking my app every time. NS is a lot more conservative between releases. 2. I don't like mixing presentation and logic, RN encourages doing so, NS does not. 3. TypeScript is a first-class citizen in the NS environment, it is not in RN. 4. Angular 2 > React 5. NS cre…

Wow, hold on guys. This enterprise dude thinks all the tooling around the RN ecosystem is very confusing. Angular 2 must be better then.

Re: Why I'm Not a React Native Developer

#214

Earlier quoted context omitted.

70% of the content is not necessarily "the most important part of the content". 2 minutes in a 5 minute animation short are the credits.

2 minutes isn't 70% of 5 minutes. It's only 40%. Yeah, nitpicking, I know.

Getting the exact percentage is not necessarily the most important part of an analogy.

Re: Why I'm Not a React Native Developer

#215
post #120

Earlier quoted context omitted.

This is definitely a specialist feeling the discomfort of not yet becoming a polyglot. Had a CTO like that once.

The author seems to express a deep enough understanding of Javascript to not warrant this dismissive critique. It's not like he's saying "Javascript sucks," he's outlining specific places where it can cause issues in development compared to the alternative.

Author seems to express a deep understanding of JS quirks and outlines specific places (often rare corner cases) that'd trip a JS beginner.

Re: Why I'm Not a React Native Developer

#216
Ok, so to 'fix it' we need React in Swift(instead of JS) without the facebook license clause. It sounds like the next UI framework. Unfortunately you can't have it all because Swift doesn't work on browser(yet, wasm will make it possible)

Re: Why I'm Not a React Native Developer

#217

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

> Please what kind of programmer would ever do this?

Someone with an interesting development development history (maybe C?), with little grasp of the idioms of newer coding styles.

Re: Why I'm Not a React Native Developer

#219

We have PureScript which is statically typed, pure functional language compiling to JS, can't it be adopted for React Native development somehow?

You really need to check out Elm. It's an ML-like language with built in functional reactive framework similar to React, but built to work naturally with the language rather than requiring the FFI binding you'd need if you use Purescript.

Elm's type systems is really constrained compared to PureScript's. It's great for people coming from JavaScript, but not so much for those coming from Haskell.

Also, you still need FFI in Elm. elm-lang/virtual-dom is basically just a wrapper around the native virtual-dom library. Also, afaik there's nothing like react native for virtual-dom.

Re: Why I'm Not a React Native Developer

#220

We have PureScript which is statically typed, pure functional language compiling to JS, can't it be adopted for React Native development somehow?

Yes, it can, although I can't say how usable those bindings are.

[0] https://github.com/arthur-xavier/purescript-react-native

[1] https://github.com/hoodunit/purescript-react-native

Post reply on HN