@chris_parjaszewski I just wouldn't call anything other than Swift & Objective-C a native technology. Yes, React Native and Xamarin are more "native" than PhoneGap in the sense that they bridge to native components instead of just being a wrapped web app, but they're still wrappers as nor JavaScript, nor C# are officially endorsed by apple, meaning Facebook and Microsoft have to wrap around the new APIs first and thus are always behind. Try writing an iOS 10 app in React Native today and you're likely to find that support for new APIs announced at WWDC is not yet there. The app is also likely to run slower, simply because of the overhead that the glue code to bridge components, (i.e. the compiled code is unlikely to be idiomatic), incurs and for a complex app with possibly hundreds of classes, you usually can't afford it if you care about user experience But most importantly, if it's a complex app of any sort, there will be time when you have to drop down to Swift/Obj-C because the React Native/Xamarin solution won't be up to pair, (so it doesn't even have the befit of being end-to-end in JS), and if you need help, everyone is going to assume Swift/Obj-C as a baseline, which will make things even more difficult. Even Facebook's own app isn't built with React Native.

Kenny Meyer - Where did I say that React Native uses web views?

Max Jaleel: Absolutely agree, depends on what you started on. However in the traditional educational setting, OO is explained much earlier than functional is, (if at all), and is also much more visible to managers at work, who can model the class hierarchy using UML and such.

I would say because OOP makes more sense to a larger group of programmers, since even the underlying machine operates "imperatively" and it's easy to see the benefits of modelling your problem domain in terms of objects similar to the ones in the real world that affect that domain, where functional programming offers benefits that are more "academical" and less easily observable by your average programmer, while the context switch required, in terms of thinking about the problem, is quite severe. (Imagine telling Jim that he cannot mutate the program state, not even talking about monads.) Another factor is that while Lisp was quite heavily pushed in the hacker community, there was never a company quite the size and marketing power of Sun, as there was for OO. Most importantly, C was not functional and C touched everything. The extension to OO in the form of C++ was quite straightforward and preserved the performance characteristics of C, whereas Haskell's performance is quite unpredictable to this day.

There are many differences, but some of the things I like the most about Swift are: Safer type system, (e.g. no nil outside of Optionals) Mutability is discouraged, (but still possible if required) Type inference No headers Better support for concurrency Easier to learn & easier to maintain Much better support for the functional programming paradigm More powerful enum types Reference compiler is open-source and development is done in the open Playgrounds, (code is executed as you type is) Linux support

If it's a somewhat complex app, I would recommend against anything but Swift or Objective-C, (Swift if you're starting entirely from scratch), because otherwise you app will simply not stack up against your native competitors in one way or another - you're at a disadvantage here, you'll always feel "not quite right" in some ways to your customers, especially if you plan to charge for the app. If what you're building is just a mobile view into an existing web app, then React Native or Ionic, PhoneGap etc. are perfectly acceptable.