261–270 of 298 posts
I am seeing something like this in Native code var { AppRegistry, Image, ListView, StyleSheet, Text, View, } = React; is this ES6 feature?
The 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.…
If I'm reading this right, any fork of this code is not covered by the patent-protection can be sued into oblivion, by Facebook themselves if they feel threatened. Wow.
Ability to fork is crucial for real life open-source projects, so having a clause like that pretty much nulls out any open-source benefit which may have been there in the first place.
Earlier quoted context omitted.
The native uibutton is made of uiviews too
Absolutely. My primary concern is with the controls feeling native. Reimplementing controls with UIViews doesn't seem much better than reimplementing them with HTML/CSS (save for performance). There's still surface area to break the illusion. Some food for thought: what if you kept HTML and CSS but instead of using a WebView to render it, you rendered the DOM manually using UIViews? You could even make overflow: scro…
React 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.
Supports Xamarin.iOS, Xamarin.Android, Xamarin.Mac, WPF, Windows Forms, Windows Phone 8 and Windows Store apps. Check out "Writing Mobile Apps the Github Way by Paul Betts" @ https://www.youtube.com/watch?v=voa44OHBKME
It is the framework that powers GitHub for Windows and various other undisclosed projects ;-)
Earlier quoted context omitted.
google "define:hereunder" -> "as provided for under the terms of this document."
With sub-qualification: >further on in a document. Even your primary definition contains the location clause, 'under the terms'.
Odd, that didn't show up in my view o_O Maybe google is geo-targetting dictionary definitions...
Also, 'under the terms of this document' does not literally mean 'physically located beneath this sheet of paper' :P
Earlier quoted context omitted.
I'vs been obsessively checking too, but for React Relay :(
It's the server-side GraphQL for me :(
Hallelujah! I've been checking my Twitter obsessively today and yesterday for this.
I'vs been obsessively checking too, but for React Relay :(
It's basically Relay but using Promises instead of GraphQL to write queries. Transmit is coincidentally also a very efficient way to create isomorphic apps that can render on the server.
Earlier quoted context omitted.
I think many people dismiss this recommendation right away nowadays, but here it goes: Adobe Air comes pretty close to "WORA". For 2D games it goes almost without saying, but throw in the excellent Starling + Feathers framework and it is great for Apps too. A drawback is of course that you do not have native UI, but if you can get passed that it works really really well. I evaluate cross platform technologies quite r…
I can see the appeal of Adobe Air and its ecosystem. I guess on mobile the only problem is binding to system services & ad providers. IIRC most of that is already covered by 3rd parties, but it's a bit involved to do it yourself. Funny you mention Flex, still gives me the shivers, still used by a lot of enterprises around here. Pretty much on par with applets in terms of badness.
But considering that you do not necessarily have any costs in developing Air (you get the compiler, and also good editors, for free) it is not that bad at all.
I also do not write native extensions myself, but at least you know there is the option in case u need to access some native library. But yes, in that case it is not really "write it once" anymore.
Earlier quoted context omitted.
My last update (from two weeks ago or so) was that you were going to bundle a JS runtime for Android as there's too much variation in earlier versions. Has that changed?
Ah- I stand corrected! I spoke with a few Android-focused folks and they set me straight. On Android, there is no JS execution environment available. We want to avoid the memory and cpu overhead of web views. So we are basically forced to ship Android with a copy of either JSC or V8.
I'm interested in this primarily because I don't find it appealing to invest in (basically non-transferable) iOS platform skills. I want to build native mobile UIs for my projects, but not with a dead-end language and tools.