Please see this image: http://facebook.github.io/react-native/img/chrome_breakpoint... I am really confused. Why is this easier - this looks extremely buggy and complex?
React Native is now open source
251–260 of 298 posts
Re: React Native is now open source
#252Earlier quoted context omitted.
Phone Gap tried to mimic native Android and iOS UI using HTML, CSS, and JS. React Native uses JS to control 100% native UI.
For some definitions of "100% native UI." I'm a little concerned because, for example, a button is not implemented as a native UIButton, and a ListView doesn't use UITableView. Instead they are composed of native UIViews with a lot of JavaScript glue. That being said, Facebook has more experience writing iOS apps than me, so it may be possible that those things don't really matter (and doesn't preclude 1:1 components…
Re: React Native is now open source
#253Earlier quoted context omitted.
Any idea what there is in React that Facebook have or are likely to have Patents over? Presumably, using another React-like framework might open you up to issues with these without the (limited) protection of the patent grant.
There is prior art, the first time I saw vdom was at Clojure Conj 2012, six months before React was publicly released. Project was called "webfui" by Conrad Barski, https://m.youtube.com/watch?v=HeI5-D7SQe8
Re: React Native is now open source
#254Earlier quoted context omitted.
Can anyone tell me how this clause is interpreted when I use React in Germany? German law (simplified) claims that no software patent is valid unless it solves a technical problem (in the physical problems sense). Does this mean since I accept German law as valid by being a citizen of the country I implicitly claim some (ergo any) Facebook patents are invalid and the clause triggers automatically? Is living in such a…
I'm pretty sure you're not making any claims in other jurisdictions implicitly — that would be somewhat terrifying. Whether the clause is triggered or not shouldn't matter if the patents aren't valid in your jurisdiction. You don't have to state your rights — you just have them (there might be exceptions to this). --- I'd love to get an answer to the bigger question as well.
Are there ever! For example, right against self-incrimination must now be invoked explicitly. Refusing to answer a question (they will say "being evasive") can be used against you unless you affirmatively state you are exercising your right to remain silent. [1]
[1] - http://www.abajournal.com/news/article/chemerinsky_silence_i...
Re: React Native is now open source
#255Re: React Native is now open source
#256Earlier quoted context omitted.
For some definitions of "100% native UI." I'm a little concerned because, for example, a button is not implemented as a native UIButton, and a ListView doesn't use UITableView. Instead they are composed of native UIViews with a lot of JavaScript glue. That being said, Facebook has more experience writing iOS apps than me, so it may be possible that those things don't really matter (and doesn't preclude 1:1 components…
The native uibutton is made of uiviews too
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: scroll; turn into UIScrollViews automatically.
Re: React Native is now open source
#257Earlier quoted context omitted.
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…
So if I have a common business logic library in Scala, could I build that into both my app and my server side? Write once, run in 2 environments?
Re: React Native is now open source
#258Earlier quoted context omitted.
The reason is not just that Apache is well established, it's that it's sane in its extent. Let's say 10 years from now Facebook decides to go on the warpath over fairly bogus patents. The EFF puts the headline patent on their Most Bogus patent busting list and then puts out the cry for "who is with us?" No company using any Facebook open source code answers. How does that make the industry safer?
Well, let's say that Facebook is using other company's code with a similar patent grant. Then Facebook can't go on the warpath in the first place. I understand there might be a chicken-and-egg problem here. But the final outcome seems optimal with this license. And someone has to go first.
Re: React Native is now open source
#259var { AppRegistry, Image, ListView, StyleSheet, Text, View, } = React;
is this ES6 feature?
Re: React Native is now open source
#260Earlier 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…
On the web you might use a div with overflow:scroll on native a scrollView.