React Native is a category error in this conversation. Either we care about the web and want the web to win, or technologies like Java, Kotlin, Swift, Objective C, and yes, JS via things like React Native will win.
-
-
Replying to @wycats @slightlylate and
The Web as a platform lost on mobile. We can help parts of it remain relevant. Especially JavaScript
1 reply 0 retweets 0 likes -
Replying to @andreasgal @wycats and
I (obviously) think it isn't totally lost; but very much losing.
2 replies 0 retweets 5 likes -
Replying to @slightlylate @andreasgal and
BTW, the way to rebuild is from product/market fit, and *that* means responsible amounts of script because most addressable market is EM.
1 reply 0 retweets 0 likes -
-
Replying to @andreasgal @wycats and
...sigh because it never embraced the actual web and kept making the same mistakes we did with Chrome Apps despite a better offer? Or some other reason?
3 replies 0 retweets 3 likes -
Replying to @slightlylate @wycats and
We just got canned before we had a chance to complete that process. It was very much meant to do just that. And we got canned because it wasn’t shiny stuff people use in the valley. Hard to build for EM
2 replies 0 retweets 0 likes -
Replying to @andreasgal @slightlylate and
I spoke to a lot of people inside the FFOS org in the years before it was shut down. Never got a single bite from anyone other than
@annevk, and a whole lot of "we'll fail if we don't ship packaged apps first" -- that was a huge, irrecoverable, strategic error1 reply 0 retweets 1 like -
Replying to @wycats @andreasgal and
I'm not claiming I knew how to run the whole project, end-to-end, better. Certainly not. But I do think focusing on emulating native (hosted apps) rather than on how to be a great web operating system (~PWA) was a mistake you could see coming.
1 reply 0 retweets 2 likes -
Replying to @wycats @andreasgal and
At least in GPU land, neither platform is good, and as client+server GPUs (or even smarter stuff) is where perf increasingly comes from, I see the days still pretty early. Unfortunately, I find web perf initiatives here 5-10years behind.
2 replies 0 retweets 0 likes
Generally speaking, the web is behind native, because the web standardizes a single API that abstracts all of the native APIs. Typically you see the web hang back until things stabilize, then make fast progress in the hands of a good champion.
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.