Live data from Hacker News

React Native is now open source

github.com

271–280 of 298 posts

Re: React Native is now open source

#271
post #252

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…

>Reimplementing controls with UIViews

If it's using UIViews, it isn't reimplementing native controls. It's using native controls, same as if it was implemented with (interface builder) .nib files. That's like saying "reimplementing html/css with html/css".

Re: React Native is now open source

#272

Earlier quoted context omitted.

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…

If you write JSX. What would be the benefit of using html anymore? Your own components can be the same on web or native. The base components might be a bit different but that isn't difficult to learn. On the web you might use a div with overflow:scroll on native a scrollView.

One of the big pieces in React Native was reimplementing flexbox positioning (they did it using randomly generated test cases in a TDD-based process; described in the "diving deeper" video iirc). So as long as you use flexbox to position your html, it should be pretty portable to react native.

Re: React Native is now open source

#273
After figuring out how to deploy to device (see AppDelegate.m), I tested accessibility and it seems there is virtually none. At least in the Movies example app, VoiceOver reads practically nothing.

How would one go about making the Movies sample accessible, or is that even possible?

Re: React Native is now open source

#274
post #7

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.…

As with the other discussions on this matter, I remain sceptical that this clause is a problem. The general argument is made that there is an implicit patent license granted when an open-source license is applied to a software product, and that this explicit patent license somehow overrides the implicit patent license (despite not being part of the license itself). I've received different advice on the matter, so YMM…

Yes, it strikes me as a fig leaf for something else. I'm not sure what, though.

Re: React Native is now open source

#275
post #254

Earlier quoted context omitted.

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.

> (there might be exceptions to this) 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...

Fortunately we germans don't have these kind of problems (yet.)

Re: React Native is now open source

#276

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.

Hey.. actually I also just got the task to integrate an Ad provider in out game and made a little research. As far as I can see almost all big companies are providing Adobe Air SDKs for integration. For Example:

https://www.adjust.com/ http://www.mobileapptracking.com/ http://www.appsflyer.com/ https://www.kochava.com/ http://www.fiksu.com/

Alright.. I am done with promoting now, I think ;)

Re: React Native is now open source

#277
post #248

Earlier quoted context omitted.

Then why say "whether or not such claim is related to the Software?" That would imply just the opposite to me.

That clause relates to the patents you own that you're suing Facebook over, not the patents Facebook owns that they're (no longer) granting you a license to. As an example, say Facebook owns patent 1234567 "Method and system for reacting natively". Google owns 7654321 "High-density computers in a data center". Google builds the new Maps app using React Native. This would infringe 1234567, except that React Native com…

Well, OK, fair, but for practical purposes it seems like the same thing.

Re: React Native is now open source

#278
post #141

Earlier quoted context omitted.

Fills the same niche as Cordova/PhoneGap or Xamarin. It's kinda the best of both. Intuitive dev process for web developers not needing to learn new paradigms. Fully native compilation for better performance than WebViews.

Are you sure they compile to native? IIUC they use JavaScriptCore on iOS, which currently doesn't JIT. Probably good enough to drive UI and you can implement performance hungry stuff in native code.

Not sure, but it's native UI at least. The demos they showed prior to release were far more responsive than any WebView based solution.

Re: React Native is now open source

#279

Earlier quoted context omitted.

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…

>Reimplementing controls with UIViews If it's using UIViews, it isn't reimplementing native controls. It's using native controls, same as if it was implemented with (interface builder) .nib files. That's like saying "reimplementing html/css with html/css".

It may be a "native control" but if you reimplement UIBUtton and have to recreate what Apple did to create it in the first place, that's where things tend to fall apart.

Re: React Native is now open source

#280
post #205

Earlier quoted context omitted.

Sounds like you've answered this yourself. You don't even have to dive into React (which has its own unique way that I'd call barely JS anymore). Have you tried Cordova / Phonegap?

"You don't even have to dive into React (which has its own unique way that I'd call barely JS anymore)." Eh, I assume you're referring to the JSX syntax. I happily don't use it at all. It's all just JavaScript functions and objects.

Yes, the JSX is "weird" to me.

But even the pure JS method. I shouldn't have said "barely JS anymore".

I'm just not a huge fan of apps built entirely in JS that spit out markup. I find it so messy personally, but also a giant brain shift too.

The commenter I was replying to wanted a way to take a web site and get it to run as an app. HTML, CSS, JS -- Cordova / Phonegap is one way to do it that requires very little rewriting of your code. At least compared to taking a HTML/CSS/JS web app and rewriting it in React.

Granted, I am no React expert and plan to give it more time soon. But at the 30k ft view, it's simpler to port your app that's already built by using Cordova. If you're going to rewrite anyway, sure, use React Native if you're already a strong JS programmer.

Post reply on HN