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

Reapp – hybrid apps, fast

reapp.io

Post reply on HN
Print view View original

41–47 of 47 posts

Re: Reapp – hybrid apps, fast

#41

Post by dustingetz »

marknutter wrote: post #31
danabramov wrote: post #18

Earlier quoted context omitted.

>They've gone so far as to abstract away the entire DOM and ignore coming standards like Web Components. Web Components don't solve the problems React is solving. They are completely different (and sometimes complementary tools). >I believe that the negative feedback on their original hybrid mobile app deeply affected Facebook as an organization and as a result they have swung so far in the opposite direction they ar…

> Web Components don't solve the problems React is solving. They are completely different (and sometimes complementary tools). No, they don't solve the same problem, but that's not what I was suggesting. What Web Components are trying to solve is the problem of sharing code, and if React doesn't play nicely with Web Components it's going to make it very difficult for React developers to partake in that sharing. Contr…

It appears to me that you are misinformed, React plays just fine with Web Components.

https://groups.google.com/forum/?fromgroups=#!searchin/react...

Re: Reapp – hybrid apps, fast

#42

Post by nwienert »

lewisl9029 wrote: post #40

Looks interesting. Although at it's current stage I feel it doesn't do nearly a good enough job at "looking native", which is one of the best things about the Ionic Framework. I do remember hearing that Ionic is looking to eventually move towards a framework agnostic approach with its components. In fact, a lot of the library code is already somewhat separated from Angular itself by layers of abstractions. I personal…

I think the themed title bar throws people off. The default iOS theme is much closer to looking like Native, and the rest of the components are very close. I'll be moving to push it as close to native as possible?

Any other reason you wouldn't use Reapp?

Re: Reapp – hybrid apps, fast

#43

Post by marknutter »

dustingetz wrote: post #41
marknutter wrote: post #31

Earlier quoted context omitted.

> Web Components don't solve the problems React is solving. They are completely different (and sometimes complementary tools). No, they don't solve the same problem, but that's not what I was suggesting. What Web Components are trying to solve is the problem of sharing code, and if React doesn't play nicely with Web Components it's going to make it very difficult for React developers to partake in that sharing. Contr…

It appears to me that you are misinformed, React plays just fine with Web Components. https://groups.google.com/forum/?fromgroups=#!searchin/react...

Exactly which part of that thread leads you to believe that "React plays just fine with Web Components". I suggest you watch https://www.youtube.com/watch?v=g0TD0efcwVg which gives a very clear picture of the current state of React/Web Component interaction, including the challenges associated with it.

edit: another good read if you're interested: http://futurice.com/blog/combining-react-flux-and-web-compon...

Re: Reapp – hybrid apps, fast

#44

Post by nwienert »

lewisl9029 wrote: post #40

Looks interesting. Although at it's current stage I feel it doesn't do nearly a good enough job at "looking native", which is one of the best things about the Ionic Framework. I do remember hearing that Ionic is looking to eventually move towards a framework agnostic approach with its components. In fact, a lot of the library code is already somewhat separated from Angular itself by layers of abstractions. I personal…

By the way, I've updated the main site with the non-themed iOS style. Also added a Mailbox demo.

I'll be putting up a comparison in the next week between Ionic/Reapp, but I think it will fare pretty well! Let me know what you think if you have time / see this.

Re: Reapp – hybrid apps, fast

#45

Post by rheng »

nwienert wrote: post #34

Hey hackers, Nate with Reapp here. I'll add some technical background. This has been a solo project of mine for the last five months. I actually was relatively green to npm and React in general at the beginning, but I've been working on this full-time since. I think it's a great testament to React's power and ease of understanding. I spent a large part of the development on the animations. Reapp has a custom animatio…

Fantastic work! It is exciting to see a project like this take off. I'm trying to dive in right now, and I noticed something interesting. Pardon my ignorance, but can you explain what this is?

module.exports = { route, routes };

I got an error when I tried to do this:

var a = {1, 2};

What is it setting in that case, since there is no concept of tuples in javascript? It doesn't seem to be an array, dictionary, or function. Appreciate any advice!

Re: Reapp – hybrid apps, fast

#46

Post by insin »

rheng wrote: post #45
nwienert wrote: post #34

Hey hackers, Nate with Reapp here. I'll add some technical background. This has been a solo project of mine for the last five months. I actually was relatively green to npm and React in general at the beginning, but I've been working on this full-time since. I think it's a great testament to React's power and ease of understanding. I spent a large part of the development on the animations. Reapp has a custom animatio…

Fantastic work! It is exciting to see a project like this take off. I'm trying to dive in right now, and I noticed something interesting. Pardon my ignorance, but can you explain what this is? module.exports = { route, routes }; I got an error when I tried to do this: var a = {1, 2}; What is it setting in that case, since there is no concept of tuples in javascript? It doesn't seem to be an array, dictionary, or func…

It's ES6 shorthand literal syntax [1], equivalent to:

    module.exports = { route: route, routes: routes };
[1] http://ariya.ofilabs.com/2013/02/es6-and-object-literal-prop...

Re: Reapp – hybrid apps, fast

#47

Post by rheng »

insin wrote: post #46
rheng wrote: post #45

Earlier quoted context omitted.

Fantastic work! It is exciting to see a project like this take off. I'm trying to dive in right now, and I noticed something interesting. Pardon my ignorance, but can you explain what this is? module.exports = { route, routes }; I got an error when I tried to do this: var a = {1, 2}; What is it setting in that case, since there is no concept of tuples in javascript? It doesn't seem to be an array, dictionary, or func…

It's ES6 shorthand literal syntax [1], equivalent to: module.exports = { route: route, routes: routes }; [1] http://ariya.ofilabs.com/2013/02/es6-and-object-literal-prop...

That explains a lot. Thank you!
Post reply on HN