Earlier quoted context omitted.
That alone makes it a non-starter
Why? (Honest question.)
So many big companies with tons of lawyers use React... surely if they do it it's fine.
Why I'm Not a React Native Developer
71–80 of 318 posts
Re: Why I'm Not a React Native Developer
#72Re: Why I'm Not a React Native Developer
#73Earlier quoted context omitted.
Why? (Honest question.)
So many big companies with tons of lawyers use React... surely if they do it it's fine.
> So many big companies with tons of lawyers use React... surely if they do it it's fine.
At best, that demonstrates that its fine...if you have lots of lawyers.
Re: Why I'm Not a React Native Developer
#74Earlier quoted context omitted.
I feel like this is some sort of signaling, a la 'no true programmer uses javascript, because types!'.
We all use it, but 'no true programmer likes javascript.' :)
I know plenty of intelligent and accomplished programmers who use and like JavaScript. I like poking fun at it every now and then, but come on.
Re: Why I'm Not a React Native Developer
#75Reasons why I am a React-Native developer:
- It works, really well.
- Iteration speed alone has helped us retain at an extremely high DAU/MAU ratio compared to years past.
- Both my apps have near 5 star rating across the board, probably the highest rated in the Sports category since we released, and none of our users notice that it is a RN app, which is really surprising b/c RN on Android is not up to par with iOS.
React-Native is not for every scenario, but I disagree with the author's final conclusion, that "the pros do not outweigh the cons". It's really quite the opposite in our case. The pros (OTA and productivity) heavily outweigh the cons.
Would love to see something better come out, but the recommended alternatives by the author wouldn't make the cut for us.
Re: Why I'm Not a React Native Developer
#76Could FB plug the cord on React once it does no longer align with its core strategy? Sure, it did it with parse.com without the least concern for the community of users/clients. The apology was to leave behind a half-cooked open source version of parse server.
The exact same thing could happen to the React community. I'd say stick to true open source projects and descentralized communities.
Re: Why I'm Not a React Native Developer
#77Article feels clickbaity with some points that have been addressed and discussed thoroughly already. These are known cons of using a javascript framework that compiles to native.
If you just want something easily replaceable, use something like cordova.
If you want perfectly native and guaranteed support, use the native SDKs.
If you want simplicity with a javascript framework that compiles to native with the concerns of it being made by facebook then use react native.
React native solves a lot of peoples problems especially if they are starting an app from scratch.
Re: Why I'm Not a React Native Developer
#78Ughhh. It's fine if you prefer statically-typed languages to dynamically-typed ones, but that's a preference, not a reason to try and say that JS is objectively terrible. Same with switch fallthrough, same with error handling, same with half his issues with JS. There are some legitimate grievances tucked in there, but the author lost me by pretending that his preferences were universal.
Plenty of JS's own failings are enough of a reason to say it's objectively terrible.
Re: Why I'm Not a React Native Developer
#79React Native Core Contributors responding and agreeing with some of the points.
https://www.facebook.com/groups/reactnativeoss/permalink/159...
Re: Why I'm Not a React Native Developer
#80Earlier 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…
"A true professional works with whatever language he needs to solve his/her problem, and shores up that language with the best tools available."
Right. And JavaScript is not that language, unless you are doing web stuff.