can we use Babel over the top of it?
If you can create a build process that outputs it's starting point to index.ios.js, I don't see why not.
React Native is now open source
171–180 of 298 posts
Re: React Native is now open source
#172React Native is the most promising cross-platform UI toolkit I've thus far encountered. Congratulations to the team that built / launched it. The reason I'm excited for it: Java promised write-once-run-anywhere, which means you are always serving the least common denominator. React Native promises learn-once-write-anywhere, which means a single team of engineers can realistically build high-quality apps using the tar…
WORA is pretty much a pipe dream, to different are the platforms and UI toolkits. One of the reasons why we heavily focus on enabling the same language(s) on multiple platforms while using the native UI toolkits with RoboVM. Funnily enough it's a different matter for games, see Unity, UE4, libGDX, Cocos2D-x etc.
Their philosophy for react is LOWA - Learn Once, Write Everywhere.
Re: React Native is now open source
#173omg...I'm so excited
still wish there was a way to develop for iOS on windows platform but I guess I will have to purchase a mac now if I want to build mobile apps
Re: React Native is now open source
#174React Native is the most promising cross-platform UI toolkit I've thus far encountered. Congratulations to the team that built / launched it. The reason I'm excited for it: Java promised write-once-run-anywhere, which means you are always serving the least common denominator. React Native promises learn-once-write-anywhere, which means a single team of engineers can realistically build high-quality apps using the tar…
React Native is the most promising cross-platform UI toolkit I've thus far encountered.
I guess a lot depends on what is meant by encountered but Xamarin would probably be a much more full featured cross platform UI toolkit than anything else out currently.
Re: React Native is now open source
#175Re: React Native is now open source
#176The first thing I do now on each Facebook open-source reveal, is to check the PATENTS file for the toxic second paragraph, to see if they've changed it. Sadly, no. I can't imagine being able to use this at any decent-sized company with lawyers. :-( https://github.com/facebook/react-native/blob/master/PATENTS See for example the discussions at https://news.ycombinator.com/item?id=9111849 (eg. https://news.ycombinator.…
This license is great since it reduces the chance of patent litigation in general.
If all companies issued code under these terms, and they all used each others' code, it would certainly make patent lawsuits impossible between them.
That might or might not be Facebook's goal in the license, but regardless, it seems like a great outcome. Likewise, avoiding that outcome might or might not be Google's reason for not using this code, but since other companies are, it seems in need of explanation.
Re: React Native is now open source
#177Cool to see this. By my count we now have, in no particular order: - React Native from Facebook ( https://github.com/facebook/react-native ) - Appcelerator's Titanium and Alloy Frameworks ( http://appcelerator.com ) - Telerik's Native Script ( http://telerik.com/nativescript ) - Xamarin ( http://xamarin.com ) As I understand it, all three of these frameworks have a JS (or C#) runtime that is compiled along with the a…
Don't forget http://robovm.com/ (basically java for ios).
Thanks for remembering and mentioning us. We don't have as huge a marketing budget as the other folks, so I'm going to shamelessly piggy back on your comment here.
We also do Scala, Kotlin, Clojure etc. and we are OSS as well (we started out as OSS). You can build unlimited apps without paying us a dime. You can also compile the entire compiler plus Eclipse/Idea/Maven/Gradle integration yourself so you aren't locked in.
We expose all iOS APIs and have a custom bridge besides JNI to make binding and subclassing of Objective-C APIs and C APIs as seamless as JNA or p/invoke, but without performance overhead. We use LLVM to compile JVM bytecode to native code directly, so performance is excellent and on par with Objective-C.
At this point you can write apps for iOS and Android, using the native UI APIs, and share business logic between them and your backend, if that's also JVM based. I personally think that using native UI APIs is best. However, for CRUD or enterprise apps you may not care about shininess, which is why our next focus will be on a cross-platform UI toolkit for Android and iOS.
You do have to pay for debugging support, interface builder integration and SLAs/hotfixing. We hope that's a fair way of supporting our OSS work.
Now I feel dirty...
Re: React Native is now open source
#178Earlier quoted context omitted.
WORA is pretty much a pipe dream, to different are the platforms and UI toolkits. One of the reasons why we heavily focus on enabling the same language(s) on multiple platforms while using the native UI toolkits with RoboVM. Funnily enough it's a different matter for games, see Unity, UE4, libGDX, Cocos2D-x etc.
Their philosophy for react is LOWA - Learn Once, Write Everywhere.
Yeah, I think they are right on the money with that.
Re: React Native is now open source
#179Earlier quoted context omitted.
FWIW it won't be cross platform, it will be a separate implementation for Android. The goal is the model, not the write once pipe dream.
True, but if you can write once at least the business logic, is is already a win
I am also wondering how much scope there is for writing generic interfaces that delegate to UI specific components as needed. I haven't done any native mobile development before so I'm not sure how possible this will end up being, but seems plausible.
Re: React Native is now open source
#180Earlier quoted context omitted.
If you're learning iOS development, stick to learning iOS development. A framework, no matter how cool and neat it is, will not replace pure iOS development for serious apps. Also ask yourself a question, do you really think you can call yourself an iOS developer when the only way you truly know how to create apps is with React?
> do you really think you can call yourself an iOS developer when... I don't really want to call myself an iOS developer. I just want to port a simple web app to iOS, and my options are learning just enough iOS development to do it myself, or hiring a real iOS developer. So I'm curious if this framework would tip the scale in favor of the first option.
Diving straight into a framework while learning the underlying system in parallel can teach you a lot about best practices and design patterns and so forth. Personally I'd say doing both is a good idea. Just make sure you learn the whys and hows for everything the framework is doing. You can vacuum up all the accumulated knowledge of the framework team.
Saying this, I have no real idea how abstracted react native is from normal IOS dev, so maybe it wouldn't be as helpful as, say, learning python and django at the same time.