41–50 of 55 posts
Still happy with Jquery-mobile , is Easy ,OOP and Better. React.js is a lost of time as many other framework that try to copy the javaBean concept. When browser support completly ES6 all this framework will be forgotten
Coming from a background of WebViews hybrid development (Cordova/Ionic), React Native simply blew my mind. How I see it is you get the UI advantages of doing native development, with the advantages of using React for the front-end just like I would for the web and going the native way whenever you need to. I don't think all projects should be done with it as native development still has its place for certain kind of…
I'm going through a similar experience. I have some experience with Objective C and iOS, almost nothing with Android and I have good experience with (non-mobile) Java. Basically I have a week to build Android app which should be quickly ported to iOS. So far my experience is mixed. React Native feels like very powerful tech. But standard library is very minimal, tooling looks very fragile (it works, but I'm very afra…
Navigation is indeed a hairy beast right now. We're working hard to get React-navigation in shape for 1.0. I think the solutions from Wix and Airbnb are fantastic -- but the community deserves a really polished, JS-only solution that's ready for production. I hope you take another look at React-Nav when we release 1.0! Disclaimer: I work on React Native, react-navigation, etc @ Expo (expo.io)
isn't Reason supposed to fill this role?
Can someone point me towards some more in-depth explorations or books on this topic?
Earlier quoted context omitted.
Obviously almost every react native app out there is accessing a SQL db over the network, and they work fine. Are you seriously saying that it's slower to get data over the react native bridge than over the internet?
No, such a claim would be complete nonsense. We are using a local database as a mirror for offline use, which is a key requirement. Profiling (a forgotten art nowadays) shows that most time spent during queries is in this bridge and not in the actual queries.
Earlier quoted context omitted.
I just gave a talk on this at uikonf. Is their anything in particular you would like to know?
Not in particular. I appreciate the suggestion of the official documentation. I do need to rtfm, however after that I will be looking for further examples and explanation. Oh, but if there is any useful tooling I should be aware of that would be quite helpful.
The Facebook React Native group is also a great resource.
>But all of this doesn’t come without a price for someone that, like me, is a heavy user of the ctrl+space code completion features of both Xcode and Android Studio. What about using Visual Studio Code with the compiler set on 'checkJs'? I've just started using TypeScript and I don't think I can ever go back to raw JS.
Same. I evangelize TypeScript whenever I can. I don't think I'll ever be as efficient in JavaScript as I am in TypeScript, now that I've tried it. Granted, it has its quirks, but (especially when writing React) it's invaluable to me.
Earlier quoted context omitted.
Assuming you don't do heavy work in the UI-loop: I find react-native's bridge memory-management on Android rather questionable: [0] They make heavy use of structures in native memory for argument-passing between JavaScript and Java. Once again someone thought they could outperform the JVM with their C-skills. My critique was dismissed :-/ Even though I showed that giving up RN's native memory and just sending seriali…
While there is a vm of sorts on Android, there's no jvm. Is your comment about Android or the (traditional) jvm?
Has anyone had experience with NativeScript? Currently trying to compare that to React Native for our next project.
React Native vs Xamarin?
Very different approaches. Personally, I'm most intrigued by what Google will show of Flutter at I/O this year.