Is there an FRP library in iOS? The author states that React "feels superior" than FRP, so I'm curious what the comparison was.
React Native: Initial Thoughts
21–30 of 105 posts
Re: React Native: Initial Thoughts
#22He knows they just released it right? A good number of "The Bad" should probably be seen as coming soon. Probably could've named those "will be better when..." Especially Stylesheet and Swift support.
Re: React Native: Initial Thoughts
#23When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.
I think you're expecting a little too much out of a one page blog post.
Re: React Native: Initial Thoughts
#24I think these are fair concerns, but it also sounds like this person comes from a more iOS native development background. Why not stick with that? I like the idea of react native as i use react more and more in the browser, and I enjoy the workflow.
> Why not stick with that? Eventually it'll be available for Android, so that's a valid reason.
I thought the APIs would still be different though. Maybe not. Either way, I think it's great for people who do use native to try new tools. But yeah I can accept that they will probably miss certain features.
Re: React Native: Initial Thoughts
#25When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.
But JavaScript is a bad language, objectively. There's little debate on that subject.
Most of us use it because we have to, even though there are much better languages available.
Re: React Native: Initial Thoughts
#26Why is Chrome Developer Tools meh?
It's something people are familiar with and has a full debugging suite
Re: React Native: Initial Thoughts
#27Earlier quoted context omitted.
Completely agreed. After reading that I was immediate put off about the rest of the article.
Why? Javascript is not without its thorns and glitches. What makes it perfect for this use, in your opinion? Is it just the general "I don't like something you like" reaction - in which case, what is it that he's wrong about here?
Who said it was perfect, for this or any other use? You're just constructing a straw man.
The actual objection, which was perfectly obvious from the comments you were replying to, is with the use of the word "Javascript" alone without any further explanation, as if it was axiomatic that the use of Javascript is bad.
When an article includes such an extreme opinion without explanation, it inevitably puts off anyone who doesn't share it. Moreover, it calls into question the ability of the author to review the technology in a fair way, and the purpose of them reviewing it at all. React Native's entire raison d'etre is to provide a native version of a web development stack. If you are inherently biased against web development technologies, then you're obviously not going to get on with React Native, or any similar technology.
Re: React Native: Initial Thoughts
#28> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. This is located in « The Meh » section. IMHO, it should be in the « The Good ». Using the official spec instead of reinventing the wheel is always a good move.
Id really like to know what a better flexbox api would be like.
Re: React Native: Initial Thoughts
#29Component-based file structure is firmly in the "good" column for me. It makes small components much more feasible.
If you're forced to split out your view, your template, your stylesheet, your controller, your model, your business logic, et cetera into separate files you are forced to keep components large.
However, if you have a component-based structure, whenever you notice a very small piece of common functionality it becomes trivial to create a new component for that functionality. You end up with a very large number of very small, very easy to understand components, with clear areas of responsibility.
Re: React Native: Initial Thoughts
#30Has anyone compared React Native to Appcelerator Titanium?