Has anyone compared React Native to Appcelerator Titanium?
It's a bit like comparing a particle accelerator to a bagel. Easier to explain them each on their own. Try running through some sample code of both to feel out the philosophy.
React Native: Initial Thoughts
51–60 of 105 posts
Re: React Native: Initial Thoughts
#52When "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.
Have you just recently stepped out of a time machine? There is quite a bit of debate on that subject.
Re: React Native: Initial Thoughts
#53Component-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 functionali…
> 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. Why exactly does this force you to keep your components large?
A typical component in my React app contains about 3 lines of HTML. Have you ever seen a 3 line HTML template?
Re: React Native: Initial Thoughts
#54OP mentions you can enable auto refresh, instead of having to Command + R every time I assume. I couldn't find that info anywhere, does anyone know how to do that? I'm really used to that workflow now with Figwheel + Om.
Yes, in the simulator if you go to the "Hardware" menu, then "Shake Gesture" while the RN app is running, it'll pop up a menu that gives you the option. It is very cool.
Re: React Native: Initial Thoughts
#55OP mentions you can enable auto refresh, instead of having to Command + R every time I assume. I couldn't find that info anywhere, does anyone know how to do that? I'm really used to that workflow now with Figwheel + Om.
Re: React Native: Initial Thoughts
#56Earlier quoted context omitted.
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 wh…
I don't think that just because someone doesn't like Javascript it makes their opinion less valid, or that they are a poor developer .. by many professional, highly-productive developers standards, Javascript is a mess and ought to be avoided. For some, the use of Javascript to solve the cross-platform web development problems is a poor decision .. whereas your argument seems to be "everyone else is doing it therefore it must be good and anyone who disagrees with the collective mind is clearly stupid".
Sure, I'd like to know why he thought Javascript is a negative. I'd also like to know why some think its a positive. But I fail to see how invalidating his entire argument is going to prompt that discussion. Seems to me like those who disagree with him about Javascript just want to shut down the whole discourse - whereas there could, indeed, be very good reasons why Javascript is a negative.
Re: React Native: Initial Thoughts
#57> Styling nested view controllers is a pain. You are taken back to the root view controller after each refresh.
It's so interesting how once you get used to instant feedback loop, anything that's longer is perceived as a pain. We want to find a solution for this though :)
Re: React Native: Initial Thoughts
#58OP mentions you can enable auto refresh, instead of having to Command + R every time I assume. I couldn't find that info anywhere, does anyone know how to do that? I'm really used to that workflow now with Figwheel + Om.
See: https://twitter.com/ryanflorence/status/582016664847290368
Awesome, thanks. That should really be mentioned in the Quick Start and/or Tutorial in the docs. I think a lot of people would really appreciate that feature. :)
Re: React Native: Initial Thoughts
#59Earlier quoted context omitted.
> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.
I think you overestimate Node's popularity, compared to other languages on the server side.
It's getting more significant. Keep in mind it's only been around for five years, and still has a very good adoption rate for a new technology.
Re: React Native: Initial Thoughts
#60> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. Flexbox is the saner API we've all be waiting for, in my opinion. I'm curious what the author's objections to it are. That's really my problem with the whole piece — statements like this are thrown out there without much justification or explanation.
I'd much rather be writing apps using constraint-based layout, much like AutoLayout. It took me a while to grok it, but it's much simpler once you get it.
It's even available in javascript: http://gridstylesheets.org/