Google/Chrome folks seem caught up now. Mozilla: honestly I don't even know how to tell.
-
-
Replying to @wycats @slightlylate and
The
@chrome team has understood for years that native is the enemy to fight. WebView wrappers like Focus don’t move the needle in this key battle. Also not sure that fight is still winnable though.@reactnative might be the future instead2 replies 0 retweets 1 like -
Replying to @andreasgal @slightlylate and
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.
2 replies 0 retweets 6 likes -
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 @wycats and
We got a lot of hard "no"s on PWA vision and support in '13/'14. Was painful to watch.
1 reply 0 retweets 1 like
Yeah, I was there and definitely a big fan of the vision (and helped where I could, but didn't work on a browser). I don't think now, after we've made so much progress, is the right time to lose hope.
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.