yeah I really question the idea that the only options are "own a browser" and "RN on the web"
-
-
Replying to @wycats @BrendanEich and
The other viable option is to throw the baby out w/ bath water and dbl down on using native SDKs.
1 reply 0 retweets 0 likes -
Replying to @jordwalke @wycats and
I believe w/out RN, this is what would often happen, yet we wouldn't even be talking about it.
2 replies 0 retweets 2 likes -
Replying to @jordwalke @wycats and
FB can afford native mostly, triplicating effort -- but still some webviews. Others can't afford.
1 reply 0 retweets 3 likes -
Replying to @BrendanEich
I think we underestimate the cost of developing a good UX for the web. Often triple.
@jordwalke@wycats@Vjeux@justinfagnani1 reply 0 retweets 3 likes -
Replying to @sebmarkbage @BrendanEich
For example the fact that image decoding is STILL not async yet. Soon. Not yet.
@jordwalke@wycats@Vjeux@justinfagnani2 replies 0 retweets 3 likes -
Replying to @sebmarkbage @BrendanEich and
image decode in a web worker + TA transfer is an abstractable workaround
2 replies 0 retweets 0 likes -
Replying to @wycats @sebmarkbage and
Guess what. We've even tried that.
2 replies 0 retweets 3 likes -
Replying to @jordwalke @sebmarkbage and
right, and it worked. Sounds like a feature not a bug!
2 replies 0 retweets 0 likes -
Replying to @wycats
actually it was too slow. Without SIMD not worth the tradeoff. When is SIMD landing?
@jordwalke@BrendanEich@Vjeux@justinfagnani2 replies 1 retweet 0 likes
what...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.