[deleted]
React Native: Initial Thoughts
91–100 of 105 posts
Re: React Native: Initial Thoughts
#92[deleted]
Re: React Native: Initial Thoughts
#93Earlier 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.
By that reasoning PHP must be amazing
Windows too.
(Disclaimer: I actually think that many facets of Windows are better than anything else, but I know many here do not.)
Re: React Native: Initial Thoughts
#94I played around with it a bit over the weekend. You can call it native, but at the same time, it's not completely native. For example, there is no UITableView support. That's one of the most common ways to present data. Hell, one of the first things I tried to do. (There is a bug report. They tried to support it but the code was ugly and didn't really play well with react-native so it was dropped). You can create a L…
So: would an instant feedback environment that is "more native" be of interest?
Re: React Native: Initial Thoughts
#95Earlier quoted context omitted.
I think you overestimate Node's popularity, compared to other languages on the server side.
How would you measure such a thing? NPM has more modules than any other language package manager, isn't that evidence that Node is at least somewhat popular?
Node modules are really, really bad compared to maven or NuGet. Most of them comprise of less than 100 lines of codes.
Re: React Native: Initial Thoughts
#96> Immutable user interface. You no longer have to track state in both the model and the view; the latter is a function of the former. As soon as the model changes, React Native re-renders a virtual tree of the view hierarchy, then applies the delta to the native views. The meaning of 'immutable' must have changed lately.
Can you help me understand which part of that you think stertches the definition of immutability too far? The developer doesn't change the UI state, it is just a pure function applied to the domain state. Is it the fast path they implemented that does the diffing to speed up the function that bothers you?
Re: React Native: Initial Thoughts
#97Earlier quoted context omitted.
How would you measure such a thing? NPM has more modules than any other language package manager, isn't that evidence that Node is at least somewhat popular?
Node modules are really, really bad compared to maven or NuGet. Most of them comprise of less than 100 lines of codes.
This is NOT a bad thing, and it's one of the things I personally love most about NPM and the node community in general.
Re: React Native: Initial Thoughts
#98Earlier quoted context omitted.
"Chrome Dev Tools. Browsers are doing too much already." I think he's trying to convey that the browser is getting too bloated and that there should perhaps be a native app to handle the debugging.
Which is daft, because to produce a separate app specifically for debugging React Native would be a huge undertaking with zero extra benefit. Chrome's Dev Tools are best in breed (IMO) and it makes sense to leverage them. If there were things being added to Chrome Dev Tools specifically to support React Native, that'd be different.
Blink Devtools are used widely. node-inspector is another isolated use case, and is quite popular.
Re: React Native: Initial Thoughts
#99Earlier quoted context omitted.
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.
> 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.
Sure, McDonalds is in fact the best food available.
Come on
Re: React Native: Initial Thoughts
#100Earlier 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?
Why, because the entire point of react native is so you can use javascript to handle your logic in your app. This lets you bring in a ton more developers for your projects than just the few people who know Objective-C/Swift. So using a project and disagreeing with it's entire purpose for existing is silly without further explanation of why javascript is bad for this type of thing. In his argument he says they should…
Maybe the point is you can easily port a web app to native.
In this case, Javascript is not the point, but the (only) available language