Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing React Native [video]

youtube.com

Post reply on HN
Print view View original

111–120 of 193 posts

Re: Introducing React Native [video]

#111

Post by eyko »

cromwellian wrote: post #95

We just demoed something similar at the GWTCreate conference, an Angular-like library called Singular ( http://daniel-kurka.de/talks/gwtcreate15/singular.pdf ) It differs in that it uses the same techniques as Google Inbox to run native code. We cross compile to Objective-C with j2objc, and cross-compile to JS via GWT, the data binding, controllers, are shared code on all platforms that run full speed native, while t…

After reading through your presentation, I have to say Singular does not look at all similar. And it's Java, so different audiences I guess. Angular in Java is not a bad idea though.

Re: Introducing React Native [video]

#113

Post by cromwellian »

eyko wrote: post #111
cromwellian wrote: post #95

We just demoed something similar at the GWTCreate conference, an Angular-like library called Singular ( http://daniel-kurka.de/talks/gwtcreate15/singular.pdf ) It differs in that it uses the same techniques as Google Inbox to run native code. We cross compile to Objective-C with j2objc, and cross-compile to JS via GWT, the data binding, controllers, are shared code on all platforms that run full speed native, while t…

After reading through your presentation, I have to say Singular does not look at all similar. And it's Java, so different audiences I guess. Angular in Java is not a bad idea though.

Similar in this sense:

1) it uses templating (in our case, HTML, Android XML, and XIB) 2) it is cross platform, runs everywhere, even server 3) it produces native apps

It's different in this sense:

1) it doesn't do DOM diffing, it does two-way data-binding 2) it's statically compiled to native code, it doesn't try to run JS in native platforms, and doesn't require any async seems between between the native platform (it's all static linkage)

There may be other differences. The audience is Java and people who want no-compromise native integration. We target 70% code sharing between platforms, but expect the UI to be rebuilt for each platform.

The core engineers behind J2ObjC were those who built Swing at Sun. We're pretty sour on the idea that write-once run-anywhere UIs are possible. Best experience dictates custom design for each frontend IMHO, and shared UI widgets may get you into an 'uncanny valley' state where you're composing the native widgets in ways that are alien to platform specific style guidelines.

Re: Introducing React Native [video]

#115

Post by rahimnathwani »

cromwellian wrote: post #113
eyko wrote: post #111

Earlier quoted context omitted.

After reading through your presentation, I have to say Singular does not look at all similar. And it's Java, so different audiences I guess. Angular in Java is not a bad idea though.

Similar in this sense: 1) it uses templating (in our case, HTML, Android XML, and XIB) 2) it is cross platform, runs everywhere, even server 3) it produces native apps It's different in this sense: 1) it doesn't do DOM diffing, it does two-way data-binding 2) it's statically compiled to native code, it doesn't try to run JS in native platforms, and doesn't require any async seems between between the native platform (…

"We're pretty sour on the idea that write-once run-anywhere UIs are possible."

The guy in the video said a similar thing. It sounds like they want people to be able to use the same tools for each platform, not necessarily share all the code.

Re: Introducing React Native [video]

#116

Post by rahimnathwani »

cromwellian wrote: post #113
eyko wrote: post #111

Earlier quoted context omitted.

After reading through your presentation, I have to say Singular does not look at all similar. And it's Java, so different audiences I guess. Angular in Java is not a bad idea though.

Similar in this sense: 1) it uses templating (in our case, HTML, Android XML, and XIB) 2) it is cross platform, runs everywhere, even server 3) it produces native apps It's different in this sense: 1) it doesn't do DOM diffing, it does two-way data-binding 2) it's statically compiled to native code, it doesn't try to run JS in native platforms, and doesn't require any async seems between between the native platform (…

"We're pretty sour on the idea that write-once run-anywhere UIs are possible."

The guy in the video said a similar thing. It sounds like they want people to be able to use the same tools for each platform, not necessarily share all the code.

Re: Introducing React Native [video]

#117

Post by rudasn »

iLoch wrote: post #79

I'm part of the group that thought "what the hell?" when I first saw the React syntax - but seeing this has completely changed my mind and I'm really looking forward to picking up React as soon as possible. If this delivers on its promises (no reason to assume it won't, seeing as it's already being used in large apps) then it's going to change the mobile development landscape. It sounded like they may even be hinting…

I too had a WTF moment when I first saw JSX but after seeing a bunch of videos from the FB team explaining the whole concept being React and Flux it just made so much sense.

After playing around with it a little bit I have to admit it's so much better than anything else I tried (vanilla JS, jQuery, Backbone, Angular, Dojo).

React (+ Flux) is possibly a great way to introduce people to web development since it avoids common pitfalls and really allows (forces?) you to think about what you are doing more clearly.

Re: Introducing React Native [video]

#118

Post by marknutter »

CmonDev wrote: post #97
marknutter wrote: post #40

Earlier quoted context omitted.

There's quite a bit of hyperbole in this talk. Some web apps do in fact come close to native, but to the trained eye of a Facebook software engineer it will feel miles behind. Your average Joe doesn't give a shit, as long as they can use the app. If they did, Facebook's Paper wouldn't have been such a flop.

Don't underestimate the users. They might use different words, but their comments and ratings will tell the story of web/hybrid suffering. Unfortunately web is not meant for apps, but for interactive documents.

Don't overestimate users either. It's very easy to build for other geeks rather than the General public. Netflix apps are almost all built using web technologies and it doesn't seem to bother most users. I think there's been an overemphasis on pixel perfect UI and on UX in general but people don't want nice UI's, they want useful apps.

Re: Introducing React Native [video]

#119

Post by edygar »

A lot of people here feels offended by new ideas. I bet that many here commented even before the end of the video, and probably never used React on real apps. Could We avoid the tribalism and territorialism, please?

Re: Introducing React Native [video]

#120

Post by sheraz »

Wow. I've been struggling to teach myself objective-c, never getting beyond the simple tutorials. So I'm happy to try this out.

I currently have an MVP in ionic framework and would love to port this over to react. Though I should say that Ionic is amazing in its own right.

Also, I tend to agree with some of the comments in this thread -- regular Joe user can't really tell the difference. Ionic on an iPhone looks damn-near close to native. Android leaves a little to be desired.

Nice work React team

Post reply on HN