Hacker News Reader

Comment by savanaly | Hacker News Reader

I'm really glad to have read this article as it actually solidifies my comfort with using React Native since it seems like a well thought out list of reasons not to use React Native, and now I know that none of them really matter that much to me.

The three main disadvantages of React native brought up are:

- lack of commitment from Facebook about maintaining it for a long time. This one is the most bothering to me but it's not a dealbreaker.

- doesn't like Javascript and its related ecosystem. This doesn't bother me in the slightest, I love modern JS.

- the whole all your patents are belong to us thing that comes up every so often. I'm not a startup founder or a lawyer so I will leave such concerns to them. If my employer wants to let me develop in React, all the better for me.

View on HN

> If my employer wants to let me develop in React, all the better for me.

Is your employer _aware_ of this particular razor blade in the candyfloss?

I know managers should check these things with legal but most of the time people sort of assume that since it's open source and everyone else is using it - it must be fine.

I'm curious, what do you love about JavaScript?

Probably that he knows it and doesn’t know Swift.

What kind of a reason is this? "Ignorance is a bliss."

The point was probably that someone with a good knowledge of one language and little or know knowledge of another favors the one they already know.

There are plenty of people who are quite happy with what they have, and they see no reason to change. Then there are people (thankfully) who are never satisfied and who keep progress rolling.

> Then there are people (thankfully) who are never satisfied and who keep progress rolling.

“Here's to the crazy ones. The misfits. The rebels. The troublemakers.”

I know many languages, including Swift and Ruby, and I've actually started to prefer modern Javascript. I really enjoy writing ES7 JavaScript with Flow or TypeScript, and everything else in the ecosystem (babel, webpack, yarn, etc.)

I will admit that Swift is a much better language, but I prefer working with modern JavaScript these days.

You can love JavaScript all you want but you'll ship more bugs than you would while using Swift, having the same experience with both languages.

Even TypeScript won't get you close to Swift's compile and runtime security.

Didn't swift only target iOS devices? Then you have to write an entire second application?

Seems like one would have 2x as many bugs with the same experience having to write the app twice in swift and then again in Java/kotlin

If it needs to be cross-platform C# and F# are way more reliable than JS.

Reply on news.ycombinator.com