5 ms·

with gpu-accelerated css transitions, requestAnimationFrame, virtual dom and web workers, the experience can be damn close. he makes it seem like "no comparison

with gpu-accelerated css transitions, requestAnimationFrame, virtual dom and web workers, the experience can be damn close. he makes it seem like "no comparison", this is provably false at least for the apps he demoed. for games, native is still necessary. what react offers beyond performance though, is definitely awesome. imo, the talk comes off a bit like a sales pitch at a pep rally.

nemothekid 12y ago
I don't know - but given Facebook's past with WebView on their flagship app I feel they would be best qualified to say whether or not those solutions once fully implemented are satisfactory. It could be the case that the features you mentioned are suitable today for web applications targeting the latest iPhone on browsers on the latest standards, but not when React was first developed.
tomocchino 12y ago
You're absolutely right that it is possible to get close. I think my main point here, (though I probably didn't cover this well enough and I was being somewhat hyperbolic, I guess), was that 'damn close' is unfortunately not the default on web, and it's actually really, really hard to get there. Sorry for coming across as a sales person. Someone tweeted about a previous presentation of mine in the past asking "who the hell is this marketing guy they had do this talk". I assure you I'm not in either marketing, or sales, I just get really excited sometimes.
- dhaivatpandya 12y ago
  I thought the talk had a nice balance of pitching the idea of native React and the technical ideas behind it.
deleted 12y ago
[deleted]
hamburglar 12y ago
You're right that it's possible to get really, really close, but the effort required is very large and best avoided if possible. Not to mention, there will always be subtle differences between your UX and native, and it sucks to be in a position where you have to defend that difference to, say, your CEO who's asking why "it just feels different." Or worse, he can put his finger on exactly why it feels different and it's some tiny glitch that's out of your control but ruins the "polish" of the app in his opinion. It puts you in the position of either busting your ass to achieve the impossible or defending mediocrity.
- weavie 12y ago
  It also sucks to explain to your CEO why it's taken so long to develop multiple versions of the apps. Theres tradeoffs for everything..
thewarrior 12y ago
Do you have any examples of apps that come damn close ?
- leeoniya 12y ago
  not full apps, but some demos off the top of my head: http://tympanus.net/Development/SidebarTransitions/ http://tympanus.net/Development/SidebarTransitions/ http://tympanus.net/Tutorials/CaptionHoverEffects/index.html http://tympanus.net/Tutorials/CaptionHoverEffects/index.html

nemothekid 12y ago

I don't know - but given Facebook's past with WebView on their flagship app I feel they would be best qualified to say whether or not those solutions once fully implemented are satisfactory. It could be the case that the features you mentioned are suitable today for web applications targeting the latest iPhone on browsers on the latest standards, but not when React was first developed.

tomocchino 12y ago

You're absolutely right that it is possible to get close. I think my main point here, (though I probably didn't cover this well enough and I was being somewhat hyperbolic, I guess), was that 'damn close' is unfortunately not the default on web, and it's actually really, really hard to get there. Sorry for coming across as a sales person. Someone tweeted about a previous presentation of mine in the past asking "who the hell is this marketing guy they had do this talk". I assure you I'm not in either marketing, or sales, I just get really excited sometimes.

dhaivatpandya 12y ago
I thought the talk had a nice balance of pitching the idea of native React and the technical ideas behind it.

deleted 12y ago

[deleted]

hamburglar 12y ago

You're right that it's possible to get really, really close, but the effort required is very large and best avoided if possible. Not to mention, there will always be subtle differences between your UX and native, and it sucks to be in a position where you have to defend that difference to, say, your CEO who's asking why "it just feels different." Or worse, he can put his finger on exactly why it feels different and it's some tiny glitch that's out of your control but ruins the "polish" of the app in his opinion. It puts you in the position of either busting your ass to achieve the impossible or defending mediocrity.

weavie 12y ago
It also sucks to explain to your CEO why it's taken so long to develop multiple versions of the apps. Theres tradeoffs for everything..

thewarrior 12y ago

Do you have any examples of apps that come damn close ?

leeoniya 12y ago
not full apps, but some demos off the top of my head: http://tympanus.net/Development/SidebarTransitions/ http://tympanus.net/Development/SidebarTransitions/ http://tympanus.net/Tutorials/CaptionHoverEffects/index.html http://tympanus.net/Tutorials/CaptionHoverEffects/index.html