News for hackers. Stuff that matters.
Re:React Native for OS X by xenadu02 on Wednesday March 30, 2016 @12:18AM (#11386937)
I sympathize with cross-platform development woes (we have this problem too) but I can't say I've ever been impressed with a cross-platform app developed using React Native (or anything else cross-platform).

A React Native app isn't horrible or bad (nothing like Java Swing) but it also isn't delightful to use. Technically you have animations and things like the cross-platform navigator. In reality, you have a lot of performance issues and strange incompatibilities due to attempting to execute animation keyframes on the JS thread (or replace the system-provided navigation bar in the case of Navigator). It isn't terribly easy on battery life either.

I'd rather write my sync and offline storage system in JS and share that across platforms while leaving the entire view layer as native code. That stuff is far harder to get right for non-trivial apps, it just isn't sexy and most web devs ignore it completely because hey - the web browser is always online!

I'm biased though. Our customers download 5-10 GB projects with millions of objects in them because when you're building a hospital the MRI room is a literal faraday cage. No such thing as internet access in there and telling the user they can't pull up plans or engineering specs because they're offline is a non-starter.

Re:React Native for OS X by hartmel on Wednesday March 30, 2016 @06:18AM (#11388222)
Am I the only one who see the same story repeated again ?

We have now Facebook, a major actor on the web, who is developping a cross-platform toolkit for application development, using OS native widgets. XUL, I miss you :) And now others try support different OS.

Mozilla created everything and they just failed to "market" it. It s at the same time a pain and a joice to see real JS applications, shadow dom, custom components, CSS based styling being the core of a toolkit while we saw XUL/XBL/CSS/native calls from Mozilla be killed a few months ago. It had its flaws, but it s a serious (but really difficult) way to go : Qt did it, Gnome did it, Microsoft did it, even Adobe tried to do. Mozilla and people involved in previous ideas and implementations deserve a special mention for their work.

We really need such technologies, and that Mozilla killed theirs was a really sad choice for me. Creating software with "simple" markup, "simple" styling rules, "simple" event/user interaction handling should be a concrete goal of decades of languages/compilers/interpreters researches.

It has a price : performance, sometimes native look&feel not perfectly accurate, supported platform must have similarities. We may hopefully reach a level where a <button> tag will cost 1% of overhead against a native call and this will be a great day. I hope these new implementations will succeed, and that the actual overcomplexity in the web developpement will not land in though.

Re:React Native for OS X by Tloewald on Wednesday March 30, 2016 @01:41PM (#11391304)
This is just another example illustrating Joel's "Strategy Letter V":

http://www.joelonsoftware.com/articles/StrategyLetterV.html

Facebook is an application / services company, so it wants its competitors to be non-existent or expensive (luckily, so far, it's more the first than the second), and its complements to be free / cheap and ubiquitous. Hardware / software / networks are its complements so it tries to make them free (give away internet access, build open source servers and routers, make cross-platform libraries, and so on).

Google is in much the same boat, and does much the same kinds of thing.

Apple is the reverse, so it wants its platform to be anything but a commodity, but apps to be free / cheap and ubiquitous (hence the App Store). Similarly, insofar as it creates differentiating development tools, it would prefer they be platform exclusive. (Swift isn't a positive differentiator; it mostly addresses a platform disadvantage, so it's free and open source.)

Re:React Native for OS X by pjmlp on Wednesday March 30, 2016 @08:31AM (#11388739)
> We may hopefully reach a level where a <button> tag will cost 1% of overhead against a native call and this will be a great day.

Also known as XAML and QML.

Re:React Native for OS X by hartmel on Wednesday March 30, 2016 @10:06AM (#11389344)
I wish it to be true :)

Disclaimer: I didn't feel the user experience you described. (and have a lot more experience with XUL than QML)

What I experienced is that actual performances of crossplatform "runtimed" toolkits are enough for desktops and acceptable for mobile devices, but the global overhead (compared to a binary using native OS widgets) exists, beginning with startup cost, memory consumption, i/o latency. In fact, the same constraints that VM-based languages have. And even more : the underlying GUI toolkit may be used in an unexpected way, strange GPU driver behaviours may pop up, how not to be bothered by OS fragmentation. And then an application may run flawlessly on a device with a given OS while on another it performs not that good.

While I think it's correct to say that VM-based languages does not have to blush in front of compiled programs when talking about raw computing performance, my experience (as an ex XUL-lover, I may be biased) make me think that this is still not true when UI is involved. Java has maybe the oldest (and most optimized ?) runtimed UI, and it does not convince me. OK, this may be a bad example : Java UIs are "runtimed" at a different layer. but seeing the length of the QML performance wiki page is a bit scary :)

Maybe the "1% overhead" is an unreachable dream, and maybe the native apps will become deprecated, but I think there are a place for improvements. How many attempts of crossplatform UI runtime exists ? Not that much. With hardware improvements, the overhead will be more and more acceptable. It s a huge work, and previous errors should be looked at (rant time : Mozilla: you should not have stopped to use native widgets - Adobe: Flex - QML: mimicking web dev like XUL did is nice !).

Though, I am really impressed by Qt and .Net SDKs and I would really love to see more free software and linux surprises from Microsoft with the Xamarin acquisition.

And, let's be utopic, the future is maybe about a standard API à-la POSIX for end-user applications, where OS vendors will agree on an app, and natively implement their own <button>, their own <menu>, their own <video>. They do if for the browser, for the "webassembly", why not for the OS ? Or the browser will be deeply integrated in OS and the "web" apps will replace all native applications. Or they'll still coexist for years.

OK, anything but embedding a webview would please me :)

Re:React Native for OS X by pjmlp on Wednesday March 30, 2016 @10:32AM (#11389510)
I got lost at the VM references.

XAML engine is native C++ code, no VM. Since Windows 8 there isn't also a VM as such on the .NET side, given the AOT compilation support.

Similarly QML is only interpreted in the free version. Commercial Qt compiles QML into native code.

Re:React Native for OS X by hartmel on Wednesday March 30, 2016 @10:38AM (#11389566)
Yes, the java comparison is not really good, I wanted to make a "runtime" analogy. I didn't know for compiled QML.
Re:React Native for OS X by pjmlp on Wednesday March 30, 2016 @02:29PM (#11391730)
You can read about the QML compiler here

http://doc.qt.io/QtQuickCompiler/

Re:React Native for OS X by cheez on Wednesday March 30, 2016 @09:57PM (#11394514)
I believe it's more correct to say that the creation of the QML object tree is compiled to C++. The rest of it is byte compiled JavaScript.
Re:React Native for OS X by pjmlp on Thursday March 31, 2016 @01:00AM (#11395086)
"Compiled Qt Quick is an elegant solution to these problems: .qml files as well as accompanying .js files can be translated into intermediate C++ source code. After compilation with a traditional compiler, the code is linked into the application binary. This entirely eliminates the need of deploying QML source code, it reduces the application startup time and allows for a much faster execution on platforms that do not permit Just-in-time compilation."

http://doc.qt.io/QtQuickCompiler/

Re:React Native for OS X by cheez on Thursday March 31, 2016 @08:44AM (#11396703)
So the JavaScript is compiled to C++? They implemented emscripten?
Re:React Native for OS X by pax_americana on Wednesday March 30, 2016 @08:38AM (#11388765)
I find it amusing that those two mirror XML and JSON respectively.
Re:React Native for OS X by pjmlp on Wednesday March 30, 2016 @08:44AM (#11388802)
We could have had XAML for the web if XHTML had been successful.

It is a pleasure not having to deal with HTML + CSS + JavScript tricks to bend the DOM to fake UI widgets.

Re:React Native for OS X by Tloewald on Wednesday March 30, 2016 @01:45PM (#11391340)
What really bugs me is that the browser keeps failing to step up to the plate. Despite everything, browsers still don't come close to supporting a first class user interface Why can't web apps have proper (native) toolbars, menus, etc. instead of "the best half-assed simulacrum you can make out of divs, css, pngs, svg, and javascript? This was the single glaring deficiency of Hypercard back in the day, and it's been faithfully replicated by the W3C et al for over twenty years now.

Sure, this would all need to be reasoned about carefully to avoid visual security loopholes, but it's not like we didn't live through Flash and Java.

Re:React Native for OS X by Aleman360 on Wednesday March 30, 2016 @10:53AM (#11389689)
cough XAML cough

Fast enough to be used by the Windows Shell, Office, Edge, HoloLens, and Xbox.

Re:React Native for OS X by jimbokun on Wednesday March 30, 2016 @10:24AM (#11389452)
"It has a price : performance, sometimes native look&feel not perfectly accurate, supported platform must have similarities."

This is what makes the whole idea a complete non-starter. Users want apps without perceptible latency for their interactions, that look and (more importantly) work like the other apps they are used to. Hard to come up with more important criteria for a successful end user application than these.

Re:React Native for OS X by hartmel on Wednesday March 30, 2016 @10:34AM (#11389523)
I really agree. I described the current state. As my next comment explain it more, there is room for improvements. Is the "write once run everywhere" paradigm a realistic goal, would it be achieved at runtime or at code generation/compilation, without an unbearable cost for users ? I want to believe.

W3C made it possible for web.

Re:React Native for OS X by cleversoap on Wednesday March 30, 2016 @07:44PM (#11393911)
> Is the "write once run everywhere" paradigm a realistic goal

A part of me sees react-native adding another option here - "write once, tailor anywhere"

While it's always been possible to have common core logic and then tweak your frontend for each platform as a separate project to get a slightly closer to actual native experience, react-native makes it significantly easier to do so and I think it's that one+ standard deviation away ease that makes all the difference.

I don't think we'll see a lot of successful react-native cross platform that goes for the one-size-fits-all approach but rather, with the same (probably even less) effort, we'll see react-native apps that target the UX of a platform rather than just the UI elements.

Re:React Native for OS X by jakevn on Wednesday March 30, 2016 @12:35PM (#11390544)
> W3C made it possible for web

W3C provided what might be akin to C compiler standards which are only partly followed by implementors.

The rest is handled by libraries/frameworks/polyfills that get you 80% of the way there.

Re:React Native for OS X by kevando on Wednesday March 30, 2016 @10:25AM (#11389466)
If you look at Apple, Google, and Facebook as competitors - I think it's clear that Facebook feels vulnerable that it does not own a programming language. I see RN as their push to create a unique "language" that people build apps in.
Re:React Native for OS X by woogley on Wednesday March 30, 2016 @10:54AM (#11389694)
That seems unrelated. It's not like Go lets you build GUI Android/iOS apps. Also Facebook has http://hacklang.org/
Re:React Native for OS X by jmhobbs on Wednesday March 30, 2016 @01:54PM (#11391422)
Re:React Native for OS X by kevando on Thursday March 31, 2016 @10:13AM (#11397283)
Sorry I misspoke calling it a programming language. I am referring to Android/Chrome/iOS/OSX so Facebook is likely trying to get into the OS game.
Re:React Native for OS X by cageface on Wednesday March 30, 2016 @12:42AM (#11387024)
I'm a big fan of React for frontend web work but I'm also not sold on React Native. It's a step up from web frameworks like Ionic but it's still a lowest-common-denominator experience that can easily be beaten by a real native app. And given that the competition for a spot on the user's home screen is tougher now than ever I don't think you can afford to be lowest common denominator unless the service behind your app is so essential that users will put up with a less than stellar app.

So I think RN is a reasonable option for some kind of business that needs a decent, usable app on both iOS and Android. But if your business is mobile-first then I would still recommend you take the time to do a real native implementation.

Re:React Native for OS X by weixiyen on Wednesday March 30, 2016 @03:28AM (#11387527)
It's really odd to read your comment and the parent comment, at least regarding the iOS side of things.

I've gotten my RN app to run at the same performance level (as far as the user is concerned) as my native app and there are definitely some non-trivial animations and gesture responders for the RN version.

It did take some tuning and I had to add a couple artificial delays to wait for animations to finish, but nothing crazy.

No opinion on Android yet, but RN for iOS is definitely not negatively impacting the user experience in my case.

It's not in the store yet, but to give you an idea of the UI complexity level - see Slack and Google Chrome's UI and gestures.

Re:React Native for OS X by briandear on Wednesday March 30, 2016 @03:49AM (#11387592)
"As far as the user is concerned.." What exactly does that mean? How do you benchmark that? Or are you just guessing?
Re:React Native for OS X by weixiyen on Wednesday March 30, 2016 @04:00AM (#11387632)
It means that the transitions between RN and Native for most cases are visually indistinguishable to the end user. Of course there are potential differences "under the hood" simply b/c the animations are implemented differently.

It's possible that the OPs ran into certain issues with specific cases or weren't able to figure out a workaround even though solutions exist, but the result of their comments unintentionally create FUD.

I'll give an example. One of the most popular libraries for messenger apps to use in RN is GiftedMessenger, but it's actually doing the keyboard wrong, so people may get the misconception that ReactNative doesn't support smooth keyboard animations, which is not true. There are a lot of examples like this, not meaning to pick on anything specific.

I will say that the library ecosystem around RN doesn't feel mature yet, kind of like Node.js in the early days, but React-Native itself is not the issue.

Re:React Native for OS X by teacup50 on Wednesday March 30, 2016 @12:07PM (#11390286)
If you require more CPU cycles to do it, then it's not indistinguishable, even if it actually winds up being visually indistinguishable.

It drains more battery, it leaves less CPU for other operations, etc.

Re:React Native for OS X by lowboy on Wednesday March 30, 2016 @12:20PM (#11390400)
Indistinguishable as far as the user is concerned. I'm guessing most users won't ascribe any battery or CPU degradation to a new app, unless they spend half their day on it.
Re:React Native for OS X by LeoNatan25 on Wednesday March 30, 2016 @04:14AM (#11387707)
I have very high doubts that they are "visually indistinguishable". Did you time animations exactly? Did you give the animations the same easing function exactly? Also, what happens when iOS 10 comes, and tweaks these values?

No, the user always feels. Even the grandmas and grandpas, that are far away from technology as possible, feel it in the back of their mind. They know something is "off".

Also, adding "artificial delays" to wait for animation end is a sign of a terrible terrible animation system.

Re:React Native for OS X by weixiyen on Wednesday March 30, 2016 @04:37AM (#11387807)
> I have very high doubts that they are "visually indistinguishable"

It's hard to describe without showing you in person and asking you to tell me which app is a RN app vs native, but it's actually the case... There's pretty granular control over the easing functions and the default ones do match the iOS curves.

I was a designer before being an engineer, and I was immersed in Obj-C for 4 years before trying React Native. On the well-implemented React Native apps, it really truly is indistinguishable.

Re:React Native for OS X by afarrell on Wednesday March 30, 2016 @05:00AM (#11387922)
Perhaps the difference here is between a RN app written by someone with only a web/js background and a RN app written by someone who has a deeper understanding of the system beneath RN's abstraction layer?
Re:React Native for OS X by weixiyen on Wednesday March 30, 2016 @07:09AM (#11388399)
That's not what I meant. It's got the right easing curves out of the box for most transitions. Sorry for the confusion. But there are definitely some things that take a little more digging around as the documentation doesn't exactly offer "best practice" recommendations in all cases.

It does help to read obj-c code in the RN repo to see what's possible and how things work so you use the right javascript parameters, but you don't normally have to do additional obj-c coding most of the time.

Re:React Native for OS X by afarrell on Wednesday March 30, 2016 @08:03AM (#11388619)
Yea, I'm offering a bit of a different point than you.

You're saying that that it is easy to use RN to build an app that is indistinguishable from an app written in obj-c

I'm offering the possibility that your 4 years of obj-c experience trained you to make intuitive judgements about how things should be done and that this intuition is mostly correct. Also that a person without that experience wouldn't make those same judgements and might default to doing things in a lower-fidelity way.

This suggestion is offered without experience using either react native, obj-c, or swift. So coming from ignorance, I might be entirely wrong.

Re:React Native for OS X by coldtea on Wednesday March 30, 2016 @10:25AM (#11389462)
>No, the user always feels. Even the grandmas and grandpas, that are far away from technology as possible, feel it in the back of their mind. They know something is "off".

If it's below a certain ms (milliseconds) threshold the user does not "feel". There's nothing more or less to it besides simple physiology.

Re:React Native for OS X by eloisant on Wednesday March 30, 2016 @04:02AM (#11387643)
It's not a lowest common denominator. You can have a different UI on Android and iOS, and share whatever code can be shared.

Additionally I like the React lifecycle better than Android's finite state machine where you always have to know where in the cycle you are, what's next and what's before, etc.

Re:React Native for OS X by cageface on Wednesday March 30, 2016 @06:50AM (#11388318)
It's using native UI elements but they're still wrapped in a higher level abstraction, which obscures details and nuances of the UI stack on each platform. You're still giving up precision and control in exchange for a cross-platform abstraction, just not as much.
Re:React Native for OS X by eloisant on Wednesday March 30, 2016 @10:19AM (#11389421)
Well, you can use a common abstraction for elements that make sense on both platforms and have platform-specific components that does exactly what you want and that you will use only in one version.

If the wrapper doesn't do what you want, you can still write that portion in native or write your own wrapper with an underlying implementation that does exactly what you want.

Re:React Native for OS X by jbhatab on Wednesday March 30, 2016 @09:41AM (#11389161)
Are you being serious? Have you seen facebook groups or discord? Both are amazing apps. Facebook groups is better than most native apps I see.

Just because the tool isn't the right tool for your job means nothing about how good it is. graph databases aren't the best at searching large singular tables, but that doesn't make them useless.

Re:React Native for OS X by RussianCow on Wednesday March 30, 2016 @10:32AM (#11389506)
I could be wrong, but I don't think Discord uses React Native; I think it just uses Cordova or one of the web hybrid platforms. And it definitely shows: performance is less than stellar, and it definitely doesn't feel like a native app to me (on Android, at least).

Edit: It looks like the iOS version is built using React Native, but the Android one is not. I can't comment on the iOS version as I've never used it.

Re:React Native for OS X by seanclayton on Thursday March 31, 2016 @03:37AM (#11395576)
The Android app is fully native because Android phones tend to have not have the single thread performance that js needs.
Re:React Native for OS X by RussianCow on Thursday March 31, 2016 @02:04PM (#11399202)
Do you have a source for this? Everything I'm finding suggests that the Android app is not native, and last time I used it (a couple months ago), it definitely didn't feel native, and performance was sub-par.
Re:React Native for OS X by eloisant on Wednesday March 30, 2016 @04:04AM (#11387653)
The thing is that when you encounter a good application based on a cross-platform toolkit, you don't know it's a cross-platform toolkit.

You only know when you notice something is wrong.

Re:React Native for OS X by LeoNatan25 on Wednesday March 30, 2016 @04:10AM (#11387689)
You know. You always know. Do you not know Atom is web based? You always feel it, no matter how good it is. It's never as good as native. It's just a deep down, "something is not right" or "something is not 100% the same" feel that you always have, be it on mobile or desktop.
Re:React Native for OS X by untog on Wednesday March 30, 2016 @05:48AM (#11388120)
You don't always know. Instagram uses webviews everywhere, I'd bet 99% of people would never guess that. I read somewhere that even the iOS messages app uses webviews, though I haven't found a citation for it.
Re:React Native for OS X by LeoNatan25 on Wednesday March 30, 2016 @10:06AM (#11389342)
It used to, but no longer on iOS. It is a `UICollectionView`. On OS X, it may still be a web view, but I am not sure.
Re:React Native for OS X by coldtea on Wednesday March 30, 2016 @10:30AM (#11389494)
>You know. You always know. Do you not know Atom is web based?

That's a bad example. There are apps where you absolutely not know. It's not even a "subjective issue".

As long as you have either

a) wrapped native widgets with the same look and behavior as native (or a fully skinned app vs a fully skinned native app)

b) response times below some objective, determined by human physiology, threshold

Then it doesn't matter if it's a higher level framework doing some wrapping, you don't know it at all.

Re:React Native for OS X by squeaky-clean on Wednesday March 30, 2016 @08:59AM (#11388894)
Have you used Visual Studio Code? It's also web based, and 100x smoother than Atom. Some applications are just slow.
Re:React Native for OS X by hamburglar on Wednesday March 30, 2016 @12:49PM (#11390716)
It's completely true that "you always know" at some level when you're dealing with a web-based "native-look" mobile app. That's why facebook ditched their effort to build their mobile apps in HTML5 a few years ago. That's why they built React Native, which, many people seem to fail to grasp, is not a web based stack. Javascript is not what's doing the hard work in a React Native app -- you can view it as a native set of UI components which are merely assembled and controlled by javascript. This is the point.
Re:React Native for OS X by bryanrasmussen on Wednesday March 30, 2016 @04:35AM (#11387795)
well, I've had that feeling with something is not right on native apps. Anyway you keep saying you, do you mean you or do you mean me? Because if you mean me the problem is I think I don't necessarily notice all the time, or I notice other problems. I'm guessing it's the same for other people.
Re:React Native for OS X by jrochkind1 on Wednesday March 30, 2016 @08:43AM (#11388800)
Eh, Slack works pretty well, and I don't know if I would have known. It may depend on the app function/domain, a chat app is maybe one you expect to look like 'the web' in the first place. Instagram too maybe, maybe apps with network connectivity/communication as their core will deal better with being implemented on web-tech based platforms.
Re:React Native for OS X by veidr on Wednesday March 30, 2016 @09:43AM (#11389177)
There are two non-native apps I use frequently on OS X, which are both rather jarring and tawdry in their deviations from the platform norms.

Slack is the second-worst offender. It feels less native than many websites do.

The other is Rubymine, which on Mac now includes its own embedded Java runtime. It's significantly worse, but they are neighbors on the spectrum. Slack suffers less because it's mostly just chat, which can be done even in a Terminal window (e.g., IRC) without suffering that badly. But when you try to do anything in Slack other than just chat, the non-native kludge factor quickly becomes obvious and irritating.

Re:React Native for OS X by arasmussen on Wednesday March 30, 2016 @01:19AM (#11387132)
The point of React Native isn't to create a delightful product experience.

The point is to create the equivalent experience of a native app with a delightful development and organizational experience.

- Instead of having separate teams develop your iOS, Android, and now OS X apps, one product team can make all three and share the majority of the code.

- Instead of a slow frustrating compile cycle you get live reloading.

Re:React Native for OS X by mbrock on Wednesday March 30, 2016 @01:45AM (#11387198)
I could write a Lovecraftian short story about my experience with React Native. Trying to turn a web app into a delightful React Native app nearly sank me into depression & burnout.

[Edited to clarify that of course I can't blame my mental health problems on a UI framework... but I keep the formulation for the sake of sympathy with anyone else who may feel less than "delightful."]

It was pretty cool at first, after a couple of months of trying to get the thing working decently without crashing, lagging, or just sucking, I gave up on the whole project.

I don't doubt that many people use React Native with delight. But there are aspects of it that are likely to cause frustration. It's a mashup of two incommensurable platforms, and in the gap between them there is horror.

Re:React Native for OS X by neoeldex on Wednesday March 30, 2016 @04:58AM (#11387912)
You do realize that React itself is only 3 years old. React native is even only about a year old.

What expectation do you have when deciding to use a framework which hasn't even released it's 1.0 yet.

Re:React Native for OS X by mbrock on Wednesday March 30, 2016 @05:13AM (#11387968)
Yeah, of course. Well, I was hopeful, based on the glowing copy and what I had heard.
Re:React Native for OS X by st3v3r on Wednesday March 30, 2016 @01:26PM (#11391097)
Then why the hell has it been released already?
Re:React Native for OS X by switch007 on Wednesday March 30, 2016 @01:36AM (#11387177)
So you're supposed to explain to your boss that the poor user experience is due to you picking something that was easier to develop with?
Re:React Native for OS X by coldtea on Wednesday March 30, 2016 @10:33AM (#11389516)
You understand that in realistic professional scenarios it's rather the boss (especially a technical boss), that will dictate that it's ok to have something easier to develop with.

Poor user experience doesn't mean much if you are not on the market soon enough.

Which should be obvious on HN, and it's a point PG himself has iterated several times...

Re:React Native for OS X by OldSchoolJohnny on Wednesday March 30, 2016 @12:16PM (#11390360)
There are a lot of devs on here with little to no real world experience or not enough to make sound judgements as far as I can tell anyway. I'm not sure if it's better to enlighten them or to ignore them since they are the sort of people that are willing to post their baseless opinions for the world to see.
Re:React Native for OS X by st3v3r on Wednesday March 30, 2016 @01:27PM (#11391110)
"Poor user experience doesn't mean much if you are not on the market soon enough."

90% of the time this doesn't apply. The "need it done last week" attitude is mostly undeserved.

Re:React Native for OS X by coldtea on Wednesday March 30, 2016 @09:53PM (#11394500)
For enterprise projects, yes. For startups competing for eyeballs, it's quite important.
Re:React Native for OS X by st3v3r on Thursday March 31, 2016 @12:43PM (#11398515)
Again, I don't believe that. A month? Sure. A week? No.
Re:React Native for OS X by hrktb on Wednesday March 30, 2016 @02:54AM (#11387420)
TBH this kind of solution is more often pushed by bosses than devs.

Any management person will throw in a "you've done X on this platform, why don't you try to reuse most of your stuff on this other platform ?", just in case it's actually doable.

Re:React Native for OS X by gurkendoktor on Wednesday March 30, 2016 @07:32AM (#11388487)
In my experience as a mobile app freelancer, many prospective clients(=bosses) insist on portable/JavaScript frameworks for new projects. I guess it is because native iOS/Android programmers are expensive, and a single JavaScript programmer rotating between platforms with a shared codebase is both cheaper and easier to manage than two or more native app programmers (at least in theory).
Re:React Native for OS X by bobwaycott on Wednesday March 30, 2016 @03:54AM (#11387609)
I feel bad for you if you've met such bosses. As one, and as someone who has worked under several, I've never once experienced a boss knowing or saying such things. I've only ever seen it come from developers.

Edit: Just to clarify, there may be instances where a mgmt type has asked if X on platform Y can be reused on platform Z easily. I've never seen it go beyond the ask.

Re:React Native for OS X by kcole16 on Wednesday March 30, 2016 @03:02AM (#11387445)
React Native doesn't deliver a poor user experience though. It's not the right choice for every project, but in most cases users won't be able to discern between RN and native.
Re:React Native for OS X by Ambroos on Wednesday March 30, 2016 @03:25AM (#11387518)
On iOS maybe, but not on Android. You have to reimplement a lot of the things you get for free when developing native apps yourself. Most animations etc, you all have to add it yourself. Problem with that is that the React Native team has some decent iOS stuff, but for Android it's all sorely lacking.

Besides Facebook's Ad Manager (which barely cuts it) I haven't seen any React Native app on Android that didn't feel horrible (and not like an Android app).

Re:React Native for OS X by briandear on Wednesday March 30, 2016 @03:47AM (#11387582)
Does the Facebook app use React "Native'? Because that app is a horrible power hog and vastly glitchy and buggy. That is a poor user experience compared to what a well written native iOS app could deliver. Users might not know its a poor experience because that can't compare to how fast and responsive the app would be if it were actually written in Swift.

There are people in this world that think Olive Garden is great Italian food. There are people in this world that think React "Native' is a good user experience.

Why does Facebook absolutely insist on avoiding writing actual native apps? As in Swift for example. It seems like they are almost allergic to actual native and instead focus on this inferior cross platform stuff.

In 'most cases' users won't know the difference? sure they will; they'll notice that the app they're using sucks more than other apps on their phone. They'll tolerate the glichiness, the occasional blank data screen during a load because they care about the content more than the terrible experience. All because a developer or the CTO somehow thinks "it works well enough" is the same as "let's really give our users the best possible experience." I am amazed that Facebook has thousands of employees but can't be bothered to write a single line of code in Swift. They've been insisting on this stubborn course of action since the beginning of their mobile experience. Does Zuckerberg just hate Obj C or Swift? Why are they making the mobile experience into the lowest common denominator? Why does their Facebook app feel like some cheap PhoneGap experiment? My Facebook app on iOS performs exactly the same as it does on a years-old Android phone.. And that's ridiculous. I have superior hardware and yet I get to run an inferior app because JavaScript? It's like socialism for apps: make everyone equally miserable.

The simple fact is this: I hate cross platform systems because they end up averaging the quantity of the mobile experience with capabilities being reduced to support the lowest common denominator. If I want my apps to run as terrible as many do on Android, I will use an Android. It's lazy development. It's a means for the JavaScript crowd to avoid leaning Swift (or Java) so they can provide middling to bad mobile apps rather than actually building the absolute highest quality product they could build.

Even Facebook does it! I feel like the React Native ecosystem is doing more to reduce the quality of the mobile app experience than anything else. Apps are being turned into these average pieces of crap with only the UI being slightly different. Does anyone have any performance benchmarks on a React "Native" compared to Swift? Any data at all? Or are we just so excited to write apps in React that we fail to care? If we care about 'cross platform' development -- we can already do that; it's called 'the web.' Let stop foisting inferior mobile apps on people just because we can.

Re:React Native for OS X by zelos on Wednesday March 30, 2016 @05:46AM (#11388114)
The Facebook app doesn't use React Native[1]. It used to be HTML5 but they rewrote it mostly native[2]

[1] https://facebook.github.io/react-native/showcase.html [2] https://www.facebook.com/notes/facebook-engineering/under-th...

Re:React Native for OS X by arasmussen on Wednesday March 30, 2016 @12:33PM (#11390520)
There are definitely parts of the Facebook app built in React Native. I built some of them. :)
Re:React Native for OS X by zelos on Wednesday March 30, 2016 @03:21PM (#11392162)
Interesting - is there an intention to rewrite the whole thing gradually and move away from native? Any reason it's not listed on the React Native site?
Re:React Native for OS X by arasmussen on Wednesday March 30, 2016 @04:26PM (#11392702)
I left Facebook almost a year ago so I can't speak about Today.

But back then internal adoption of React Native was definitely accelerating rapidly and it was solving very real organizational and developer experience problems. The original motivation of the project internally was to solve developer experience pains, just like React but for mobile.

- With such a large app (Facebook), the compile cycle was becoming quite slow. RN has no compile cycle.

- You've got 3 teams (web, iOS, Android) per product (eg. Events, Groups, etc) and they don't really communicate or share any product code despite building effectively the same thing.

Take the Mobile Ads Manager app: Now one team (of web engineers) can ship an app on iOS and Android, while sharing 83% of the code between each app, in half the time the project had budgeted for just the iOS pure native app. Not to mention the team constantly loved their jobs because they didn't have to wait 5 minutes for the damn thing to compile every time they made a change.

Re:React Native for OS X by code-antagonist on Wednesday March 30, 2016 @05:34AM (#11388066)
The Facebook app for iOS is actually mostly Objective-C [1] / Objective-C++. [2]

[1] http://quellish.tumblr.com/post/126712999812/how-on-earth-th... [2] http://componentkit.org/

Re:React Native for OS X by pcwalton on Wednesday March 30, 2016 @04:20AM (#11387731)
JavaScript is faster in most cases than Objective-C.

(I'm not going to dispute that cross-platform toolkits can have less native fidelity than compared to coding to the native toolkit can. I just don't like the Objective-C vs. JavaScript performance myth.)

Re:React Native for OS X by robenkleene on Wednesday March 30, 2016 @07:43AM (#11388529)
Huh? What's the Objective-C vs. JavaScript performance myth?

Here's a link showing Objective-C beating JavaScript handily: https://medium.com/@harrycheung/mobile-app-performance-redux...

But is this even a debate? Wouldn't you expect a compiled, manual memory managed, language to be faster than an interpreted language with garbage collection?

Re:React Native for OS X by pcwalton on Wednesday March 30, 2016 @12:47PM (#11390690)
That's an interesting benchmark, and I'd need to dive into the details to see what is going on. Perhaps there is some sort of JIT slow path. I would not expect method-heavy Objective-C to beat JavaScript. In general:

> But is this even a debate? Wouldn't you expect a compiled, manual memory managed, language to be faster than an interpreted language with garbage collection?

Objective-C is not compiled in terms of method dispatch, nor it is manually memory managed. Instead, all method dispatch happens through essentially interned string lookup at runtime, backed by a cache. Objective-C also has a slow garbage collector--atomic reference counting for all objects. (Hans Boehm has some well-known numbers showing how slow this is compared to any tracing GC, much less a good generational tracing GC like all non-Safari browsers have.)

The method lookup issue has massive consequences for optimization. Because JavaScript has a JIT, polymorphic inline caching is feasible, whereas in Objective-C it is not. It's been well known in Smalltalk research since the '80s that inline caching is essentially the only way to make dynamic method lookup acceptably fast. Moreover, JavaScript has the advantage of speculative optimization: when a particular method target has been observed, the JIT can perform speculative inlining and recompile the function. Inlining is key to all sorts of optimizations, because it converts intraprocedural optimizations to interprocedural optimizations. It can easily make 2x-10x of a difference or more in performance. This route is completely closed off to Objective-C (unless the programmer manually does imp caching or whatnot), because the compiler cannot see through method lookups.

Apple engineers know this, which is why Swift backed off to a more C++-like model for vtable dispatch and has aggressive devirtualization optimizations built on top of this model implemented in swiftc. This effort effectively makes iOS's native language catch up to what JavaScript JITs can already do through speculation.

Re:React Native for OS X by robenkleene on Wednesday March 30, 2016 @02:25PM (#11391693)
Thanks for the detailed response, to summarize it sounds like your position is that:

1. Objective-C's compile time memory management is actually slower than JavaScript's garbage collection.

2. The performance consequences of Objective-C message sending are greater than JavaScript's JIT compilation. And furthermore, that JIT compilation is actually an advantage due to the other optimization techniques it enables.

I'd like to see a more direct comparison with benchmarks, but I can see where you're coming from.

Re:React Native for OS X by pcwalton on Wednesday March 30, 2016 @02:29PM (#11391729)
Right. Note that this advantage pretty much goes away with Swift. Swift is very smartly designed to fix the exact problems that Apple was hitting with Objective-C performance.

I realized another issue, too: I don't think it's possible to perform scalar replacement of aggregates on Objective-C objects at all, whereas JavaScript engines are now starting to be able to escape analyze and SROA JS values. SROA is another critical optimization because it converts memory into SSA values, where instcombine and other optimizations can work on them. Again, Swift fixes this with SIL-level SROA.

Re:React Native for OS X by randommodnar on Wednesday March 30, 2016 @08:19AM (#11388695)
Actually JavaScript is compiled JIT by most engines these days. While it's not the fastest, it certainly can be quite fast.
Re:React Native for OS X by robenkleene on Wednesday March 30, 2016 @11:24AM (#11389955)
I see, good point, but then I'd expect the cost of JIT compilation would still have a performance cost? As opposed to Objective-C being compiled before distribution to the client?
Re:React Native for OS X by pcwalton on Wednesday March 30, 2016 @12:50PM (#11390736)
JIT compilation cost is minimal in practice due to tiered JITs.
Re:React Native for OS X by w0utert on Wednesday March 30, 2016 @08:30AM (#11388733)
Source please, because unless you have anything to back this up, your claim can only be considered grade-A FUD.

Sometimes I feel like using JavaScript too much transports people to some kind of imaginary JavaScript fairy land full of rainbows and unicorns. I read the craziest things about JavaScript development even though I can't comprehend why so many people believe it has any redeeming positive qualities over other languages, besides ubiquity.

Re:React Native for OS X by pcwalton on Wednesday March 30, 2016 @12:52PM (#11390756)
See my reply to the sibling comment for the explanation. There haven't been enough cross-language benchmarks here to say definitively, but as a compiler developer I can tell you the method lookup issue is really fundamental and in fact is most of the reason for Swift's (eventual) performance advantage over Objective-C.
Re:React Native for OS X by w0utert on Thursday March 31, 2016 @09:39AM (#11397031)
I've read your explanation, but I'm not convinced they support your assumptions (which, barring any benchmarks that make them factual, is what I consider them to be).

I'm aware of the dynamic dispatch overhead of Objective-C, but first of all it's my understanding that Apple's Objective-C runtime & compiler perform all kinds of smart tricks to reduce the overhead to a minimum (caching selector lookups and such), and second, because Objective-C does not require you to use dynamic dispatch if performance is a concern. No one is preventing you from doing plain-old C-style functions for performance criticial sections.

I also don't buy the 'ARC is slower than GC' argument. ARC reference counting on 64 bit iOS, as implemented using tagged pointers, has almost zero overhead for typical workloads. Only if you would write some kind of computational kernel that operates on NSValue or whatever (which is a dumb idea in any scenario, about as dumb as writing such a thing in JavaScript) you would ever even see the difference between not having any memory management at all. Just like your other performance claims: without data, there is nothing that backs up your statement that ARC is slower than GC for typical workloads. Hans Bohm is not the most objective source for such benchmarks by the way.

Apart from that you seem to spend an awful lot of effort explaining the things that would make Objective-C slower than JIT'ed JavaScript, while completely disregarding the overhead all this JIT'ting, dynamic typing, etc has, and the fact that in JavaScript you basically have no way to optimize your code for cache friendliness or whatnot.

You may be a compiler developer, but based on your comments I'm highly doubtful you are aware of how much optimization already went into Apple's compilers, which greatly reduce the overhead of dynamic dispatch and ARC.

Re:React Native for OS X by pcwalton on Thursday March 31, 2016 @12:44PM (#11398529)
> second, because Objective-C does not require you to use dynamic dispatch if performance is a concern. No one is preventing you from doing plain-old C-style functions for performance criticial sections.

That's just writing C, not Objective-C. But if we're going to go there, then neither does JavaScript. You can even use a C compiler if you like (Web Assembly/asm.js).

> ARC reference counting on 64 bit iOS, as implemented using tagged pointers, has almost zero overhead for typical workloads.

No, it doesn't. I can guarantee it. The throughput is small in relative terms, I'm sure, but the throughput would be smaller if Objective-C used a good generational tracing GC.

(This is not to say Apple is wrong to use reference counting. Latency matters too.)

> Just like your other performance claims: without data, there is nothing that backs up your statement that ARC is slower than GC for typical workloads. Hans Boehm is not the most objective source for such benchmarks by the way.

There's not much I can say if you're determined to discount real numbers solely because Hans Boehm provided them. But here you go ("ARC" is "thread safe"): http://www.hboehm.info/gc/nonmoving/html/slide_11.html

Anyway, just to name one of the most famous of dozens of academic papers, here's "Down for the Count" backing up these claims: https://users.cecs.anu.edu.au/~steveb/downloads/pdf/rc-ismm-... Figure 9: "Our optimized reference counting very closely matches mark-sweep, while standard reference counting performs 30% worse." (Apple's reference counting does none of the optimizations in "Down for the Count".)

Here's the Ulterior Reference Counting paper, showing in table 3 that reference counting loses to mark and sweep in total time: http://www.cs.utexas.edu/users/mckinley/papers/urc-oopsla-20...

memorymanagement.org (an excellent resource for this stuff, by the way) says "Reference counting is often used because it can be implemented without any support from the language or compiler...However, it would normally be more efficient to use a tracing garbage collector instead." http://www.memorymanagement.org/glossary/r.html#term-referen...

This has been measured again and again and reference counting always loses in throughput.

> You may be a compiler developer, but based on your comments I'm highly doubtful you are aware of how much optimization already went into Apple's compilers, which greatly reduce the overhead of dynamic dispatch and ARC.

I've worked with Apple's compiler technology (clang and LLVM) for years. The method caching in Objective-C is implemented with a hash table lookup. It's like 10 instructions [1] compared to 1 or 2 in C++, which is a 3x-4x difference right there. But the real problem isn't the method caching: it's the lack of devirtualization and inlining, which allows all sorts of other optimizations to kick in.

Apple did things differently in Swift for a reason, you know.

[1]: http://sealiesoftware.com/msg/x86-mavericks.html

Re:React Native for OS X by w0utert on Thursday March 31, 2016 @05:11PM (#11400580)
That's again a lot of information showing why Objective-C is not the most efficient language possible for all use cases, but it still does not provide any evidence why JavaScript would be faster. I'm not disputing the individual points you made, but in the context of comparing overall performance of Objective-C vs. JavaScript it doesn't say much at all. It mostly shows Objective-C will always be slower than straight C/C++, nothing about JavaScript performance. I appreciate the thorough reply though.

One thing I do want to make a last comment about is your dismissal of using C/C++ inside Objective-C programs as some kind of bait-and-switch argument. Using C/C++ for performance critical sections is IMO not the same as calling out to native code from something like JavaScript, or writing asm.js or whatever other crutch you could use to escape the performance limitations of a language. As a superset of C, mixing C/C++ with Objective-C is so ingrained in the language you have to consider it a language feature, not a 'breakout feature'. Nobody who cares about performance writes tight loops using NSValue or NSArray, or dispatches millions of messages from code on the critical path of the applications performance (which usually covers less than 10% of your codebase). As an example, I'm currently writing particle systems in Objective-C, but it wouldn't even cross my mind to use anything but straight-C arrays and for loops that operate directly on the data to store and manipulate particles. This is nothing like 'escaping from Objective-C', as all of this is still architecturally embedded transparently inside the rest of the Objective-C code, just using different data types (float * instead of NSArray) and calling conventions (direct data access instead of encapsulation). It's more like using hand-tuned data structures vs STL in C++, than like calling native code or writing ASM.js from Javascript.

Re:React Native for OS X by st3v3r on Wednesday March 30, 2016 @01:28PM (#11391127)
No, it's not.
Re:React Native for OS X by the_gipsy on Wednesday March 30, 2016 @03:58AM (#11387627)
I've seen cordova/phonegap being used as a MVP. Then slowly some screens got rewritten in their native platforms, starting with the most critical ones.

All by manager's and client's decision. It was a horrible experience overall.

Re:React Native for OS X by bmelton on Wednesday March 30, 2016 @02:20AM (#11387307)
Exactly. Except, the time to do it is before you decide on a tool, when the company is comparing time to value vs. quality.

Whether or not the experience is great isn't a deal-breaker, it's a factor in the decision making process. For plenty of companies out there, having a less-than-perfect application that they can deploy to many platforms in a month or two with a single or couple of developers is a choice that might get made, when the alternatives are either much longer timetables or many more dollars.

Re:React Native for OS X by cballard on Wednesday March 30, 2016 @09:31AM (#11389081)
Using a language in which 1 + "1" == "11" instead of one of the best type and null-safe languages to be developed in the past few years is not exactly my idea of a delightful experience, but interface as a pure function of state is a good idea.
Re:React Native for OS X by briandear on Wednesday March 30, 2016 @03:59AM (#11387630)
So degrade the experience just to make the product team happy? What product team worth a darn would actually be ok with that?

Did we forget the customer somewhere? What ever happened to trying to wow your customers rather than simply tolerating them?

This attitude makes me crazy angry. That one comment just revealed everything that's wrong with many product companies: just give the user a 'good enough' experience. If you aren't striving to create a delightful user experience than you're disrespecting your users. Laziness.

If Steve Jobs had heard you say that, he would have fired you in an instant -- and for good reason. We owe our users a delightful experience, giving them anything less is just unacceptable.

Re:React Native for OS X by jon-wood on Wednesday March 30, 2016 @04:07AM (#11387665)
A product team with limited time and money. We'd all love to have best in class apps on every platform, but there's only so many hours in the day, and only so many developers on the team. At some point we have to make tradeoffs, and sometimes the right one is to deliver something imperfect now rather than perfection later.
Re:React Native for OS X by arasmussen on Wednesday March 30, 2016 @12:35PM (#11390538)
> So degrade the experience just to make the product team happy?

Which part of "equivalent" did you miss?

You're entirely missing the point. This isn't about product experiences whatsoever. You can ship equivalently delightful experiences in React Native as you can in pure native apps. The point of React Native isn't to make your app more delightful.

The point is to develop it faster, in a more enjoyable manner, and enable one product team to develop for multiple platforms. This is an incredible win organizationally and for developer experience.

> Steve Jobs would have me fired

Check your ego.

Re:React Native for OS X by st3v3r on Wednesday March 30, 2016 @01:30PM (#11391145)
If the product team isn't happy, then the product isn't getting made. If the product team gets burnt out halfway through development, it shows.
Re:React Native for OS X by rimantas on Wednesday March 30, 2016 @03:26AM (#11387521)
And the result is they share the majority of the code and do not share the gazillion of tweaks for each plafrom, thus negating any advantage gained?
Re:React Native for OS X by alexkavon on Wednesday March 30, 2016 @01:32AM (#11387163)
> I sympathize with cross-platform development woes (we have this problem too) but I can't say I've ever been impressed with a cross-platform app developed using React Native (or anything else cross-platform).

Do you feel the same way about Xamarin? I'm just curious as I've been considering moving to it. My company has been developing on Ionic the past year or so and it's become quite cumbersome as a platform. Basic apps look alright in Ionic, but is plagued by web view problems, making a non believer in the platform. Xamarin seems to compile better and avoid the web view. I guess I'm just looking for opinions.

Re:React Native for OS X by blub on Wednesday March 30, 2016 @04:47AM (#11387851)
Any 3rd party solution will have some issues. Whenever you see mostly positive testimonials, you should be both suspicious and scared, because it means you will be the one to find those issues in production, and you won't find any help on the internet.

That was a long time the case for Xamarin, but if you look at their customer forums, reddit, stackoverflow etc you will find the negatives too nowadays.

I am not interested in .NET, so I would not personally use Xamarin anyway, but I know that with Qt for instance you have to be careful with mobile UIs - it's best used for custom stuff and not native-looking apps.

Re:React Native for OS X by m_fayer on Wednesday March 30, 2016 @05:35AM (#11388071)
I use Xamarin regularly, and it's true the primary downside is frequent bugs and regressions along the entire toolchain, and in the Xamarin wrappers of native APIs. That said, it's improved by leaps and bounds in since last Summer. It's gone from "I'm about to dump this platform any day now" to "minor nuisance", and most of the time you can just get on with your work.
Re:React Native for OS X by dcveloper on Wednesday March 30, 2016 @07:58AM (#11388594)
I second the regression issue. Particularly if you use Xamarin.Forms. The Forms navigation stack is full of memory leaks as well.
Re:React Native for OS X by m_fayer on Wednesday March 30, 2016 @04:12PM (#11392581)
For the record, I use Xamarin "classic" and not forms, and my comment was in reference to that. Given the age of X.Forms, what you say sounds par for the course.
Re:React Native for OS X by pjmlp on Wednesday March 30, 2016 @08:39AM (#11388772)
If you are comfortable with C++, a good option is to place as much as possible in C++ and then use Objective-C++, JNI and C++/CX to integrate with the native UIs from iOS, Android and WP.

Although Android is going to give you most headaches of those three, as the NDK is pretty anemic and JNI is not that friendly, but with help of JUCE and Djinni the pain isn't that hard.

The advantage is that you get to write a portable application without extra third party layers and have full support of the available SDK tooling for debugging issues.

Re:React Native for OS X by skrebbel on Wednesday March 30, 2016 @01:44AM (#11387197)
You realize that React Native also avoids the web view, right? Its more like Xamarin-for-JS with a ui kit built in.
Re:React Native for OS X by hire_charts on Wednesday March 30, 2016 @11:40AM (#11390079)
I have a question. How would you know when you're using an iOS or Android app developed with React Native? Is it possible that you're only unimpressed when you actually notice something is off?

Because, in my experience, React Native is the first framework that actually feels native, and often results in apps that behave identically to their native counterparts. One of the big reasons for this is that it actually is using native components in most places.

Facebook's philosophy isn't that you should write platform-agnostic components and use them everywhere. They actually encourage using platform features wherever possible, but at the same time the way you write the components doesn't change across platforms -- "learn once, write anywhere."

Re:React Native for OS X by TeeWEE on Wednesday March 30, 2016 @04:44AM (#11387838)
I totaly agree with you. What web-devs often forget is that native (mobile apps) have a very different runtime environments, things come and go (onCreate, onDestroy). Memory gets destroyed and reused. You need to think about background processes, multithreading. App startup is of upmost important. (starting a web page takes a lot of time, people every noticed that ios-chrome only has one page in memory at a single point ?). Its just a different mindset. The webbrowser is an abstraction on top of UI toolkits, with a very dynamic rendering engine, and simplified execution environment.

Once you have a a hammer (javascript), it doesnt mean you should apply it everywhere.

Re:React Native for OS X by Wintamute on Wednesday March 30, 2016 @05:31AM (#11388054)
tl;dr React Native doesn't use browser.

It's not clear from your comment whether you're familiar with React Native architecture or not. A React Native app works by using JS/React as the "brains" of the app (http services, state, smart components) and runs this in a separate thread to a 100% native portion of the app that uses uses platform specific native ui controls. Animation performance is pretty good because of this multithreaded approach. So in this way your JS app brain can be portable across platforms, while the nitty gritty view layer may shift to accommodate the capabilities of the native components you work with on each platform.

Re:React Native for OS X by jaxondu on Wednesday March 30, 2016 @07:10AM (#11388405)
React Native (RN) is not for all apps, it has its uses if what your app does is mainly text delivery, example news app. One of the more complicated app that uses React Native is Discord for iOS (http://stackoverflow.com/questions/35309471/is-discord-mobil...), a Slack like chat app. That was then but I'm not sure the latest version is still RN heavy. You can actually build a native iOS app, and then add RN as part of your app. The tweet by Discord that said they are using RN is deleted.

Some reservations to choose RN: RN is possible due to the JavaScriptCore framework build by Apple. It is the bridge between JavaScript code and Cocoa API. Apple designed this so that you can use JavaScript as scripting language for Cocoa. The popular Sketch for OS X is using the precise JavaScriptCore to power its plug-in scripting feature. I guess Apple never have thought JavaScriptCore could be used the way RN does. Choosing RN means your app is relying on Apple's decision on JavaScriptCore API. Someone please enlighten me if RN is still possible or not if Apple remove JavaScriptCore.

JavaScriptCore opens up the Cocoa API, but does not give you a JavaScript ready API. So RN has to implement the bridge internally. So when iOS 10 is released, you will have some lag waiting for new features or changes to be supported by RN. I guess this is common problem to all cross-platform framework.

In order to implement RN for Android, Facebook implements its own JavaScripCore for Android. I have no Android experience, but what I read is RN app for Android is not performing as natively as its iOS counterpart.

If your business rely on all Apple's platform, then choosing RN does not help as there is no RN for watchOS and tvOS.

React Native will make app manager and web-dev team happy, but not those who treasure the last mile UX experiences. But is could also be useful for those startups creating their first MVP. Get app release fast and then change to native codes when you got the traction. Is this good or bad startup advice?

It will be a different ballgame if Facebook announce they are moving to use 100% React Native for Facebook for iOS app.

Re:React Native for OS X by jhgg on Wednesday March 30, 2016 @07:37AM (#11388505)
I work at discord. The app is still react native. We use component kit for chat messages view though. But this was because early react native when we built it couldn't do what we wanted to. May switch to full RN soon.
Re:React Native for OS X by underwater on Wednesday March 30, 2016 @01:34AM (#11387170)
What React Native apps have you tried?
Re:React Native for OS X by wuliwong on Wednesday March 30, 2016 @10:45AM (#11389618)
Facebook's Groups app.
Re:React Native for OS X by zkhalique on Wednesday March 30, 2016 @01:26AM (#11387147)
I agree that sync and offline storage is hard to get right. We developed a whole general-purpose platform to do exactly this, in a way that also supports multiple users, decentralized publishing, offline storage, synchronizing messages, optimistic updates etc.

And unlike Firebase, Parse et al it is based on posting messages to streams that people join, rather than diffing objects. This way you can have a history of changes, and just focus on implementing the front end handlers for the changes.

Re:React Native for OS X by mbrock on Wednesday March 30, 2016 @01:35AM (#11387174)
Are these messages kind of like Redux actions, i.e., arbitrary domain events with semantics defined by pure JavaScript functions?
Re:React Native for OS X by zkhalique on Friday April 01, 2016 @01:05AM (#11402776)
You could describe them that way. Here is how we describe them:

http://qbix.com/platform/guide/messages

Re:React Native for OS X by KingMob on Wednesday March 30, 2016 @04:46PM (#11392857)
I can imagine there not being great internet while you're building a hospital, but you know MRI rooms aren't that large, right? If you need to leave the Faraday cage, you just walk 10 feet.

Your customers are probably downloading GBs of data in advance because their reception/speeds outside the MRI room aren't sufficient.

Re:React Native for OS X by xenadu02 on Wednesday March 30, 2016 @11:43PM (#11394839)
I was making a glib comment to sum up the entirety of the issue. I actually typed up the full pedantic explanation, then deleted it. I told myself it was superfluous prose. Guess I was wrong!

Yes, the problem is that connectivity is often absent, poor, or slow combined with the fact that the app is useless without the entire dataset available. And you're collaborating with a team, so you have 10s-1000s of disconnected clients.

Re:React Native for OS X by Kiro on Wednesday March 30, 2016 @05:24AM (#11388020)
> I'd rather write my sync and offline storage system in JS and share that across platforms while leaving the entire view layer as native code.

Of course, who wouldn't? The problem is resources. The alternative to not horrible/bad (React Native) for many devs is either horrible/bad (Ionic etc) or nothing.

Re:React Native for OS X by hollerith on Wednesday March 30, 2016 @09:52PM (#11394495)
>when you're building a hospital the MRI room is a literal faraday cage. No such thing as internet access in there

No such thing as Wifi, sure, but why can't the hospital run ethernet into the room?

Re:React Native for OS X by xenadu02 on Wednesday March 30, 2016 @10:58PM (#11394692)
Because the building is under construction and there's no conduit... Or working power for that matter.
Re:React Native for OS X by Benjamin_Dobell on Wednesday March 30, 2016 @12:39AM (#11387014)
Agreed.

If people want to use reactive programming for their view layer on iOS or OS X then ReactiveCocoa is probably a nicer fit.

Re:React Native for OS X by dhruvtv on Wednesday March 30, 2016 @12:46AM (#11387034)
React != reactive programming.
Re:React Native for OS X by Benjamin_Dobell on Wednesday March 30, 2016 @03:41AM (#11387562)
I didn't say it did...?

EDIT:

I mentioned "reactive programming" because React is typically used in conjunction with reactive programming. Mentioning something related to something else is pretty standard communication.

To elaborate on why I made my initial comment...

Reactive programming is a paradigm, it has advantages (and disadvantages). Paradigms are higher level than implementations (libraries), or even a programming languages. When people start a new project they come up with requirements; continuous integration, easily testable etc. These requirements are mostly satisfied by a paradigm, not a implementation, nor even a programming language.

If you've decided you like React, you probably like it for various reasons, most of which are probably because you're following the reactive programming paradigm - and perhaps because you like JavaScript. Nonetheless, when you start a new project (e.g. you've decided you want a native Mac app) it's your job as a competent software developer to determine the best fit for the project. This means you should really do your best to make a well rounded assessment of the situation - that means being educated about the subject matter. My comment merely agreed with the parent comment's description of the disadvantages of a (near) pure JS solution, and proposed ReactiveCocoa as an alternative that provides many of the advantages and familiarities of React, minus the disadvantages the parent post pointed out. Of course, you can't use JS to write your app - that may well be deemed by your team as a sufficient enough disadvantage to avoid ReactiveCocoa as a solution.

Re:React Native for OS X by neoeldex on Wednesday March 30, 2016 @05:05AM (#11387943)
React has very little to do with reactive programming. It definitely has similarities, but in React you do not map the dataflow in the same way you would in reactive programming. Only the flow of data through components could be considered reactive.

The real dataflow in reactive programming which could be considered the 'state', is not managed by React at all. You could use Redux for that, but having a datastore with reducers which modify state, and actions which trigger reducers is not something I would consider reactive.

Re:React Native for OS X by xenadu02 on Wednesday March 30, 2016 @11:45PM (#11394847)
Funny enough we are moving to a flux-style model for our view layer and using RAC signals for async stuff. The syncing and database logic is in a separate library that the main app treats as its official "API". That makes most of the interactions akin to Async Action Creators.
Re:React Native for OS X by vinnymac on Wednesday March 30, 2016 @01:06AM (#11387088)
To add to this, for anyone who is interested in using javascript to do reactive programming lookup rxjs or baconjs.