Investment levels predict outcomes. Multiple impls require multiples on base impl investment + fixed compat (tests, standards) overhead. Our proprietary competition doesn't bear these costs. OSS is one cost-sharing approach; we can imagine others.
-
-
Replying to @slightlylate @plinss and
In a scenario where the web is succeeding, all of these costs are investments in resilience. In scenarios where it's losing, they look more like competitive drag. So we should try to situate ourselves in the competitive analysis and weigh up risks from that perspective.
2 replies 0 retweets 1 like -
Replying to @slightlylate @plinss and
I wonder if maybe we'd benefit from some independent reliable source of data and analysis on the health and competitiveness of the web platform? I respect the "we shouldn't believe the web is in trouble just because Google says so" argument.
2 replies 1 retweet 6 likes -
Replying to @RickByers @slightlylate and
Data I’ve seen seem great. Desktop web is obv fine. Mobile web: users spend a huge % of their time on a tiny number of apps (Facebook, Twitter, Insta) and use the web for most other things. I don’t see the problem, but I’m not Google so I may not be looking for the right things
3 replies 0 retweets 4 likes -
Replying to @AdamRackis @RickByers and
Even if "Web" is losing v. "native" (category error, see next tweet), the record over ten years of overheated claims to push stuff (remember SOE and O.o? I do) that clearly 1/ wasn't ready; 2/ wouldn't help v native much or at all, disqualifies Google from being in sole overboss.
3 replies 0 retweets 11 likes -
Replying to @BrendanEich @AdamRackis and
Rick's list (FB, Twitter, Insta) shows one service that (thanks to Google PWA work) does better on Web than native for me on most of my devices (Twitter). The other two have common owner who is Web-hostile but needs it for one (FB) app still. Says more about FB than Web v native.
3 replies 0 retweets 6 likes -
Replying to @BrendanEich @AdamRackis and
This in turn says more about what's been causing years of panicked "make us overboss" premature standards pushes: FB threatens Google. Native apps always have more power & OS API support. Categorically different, inevitably so. We must reject advanced persistent threats via Web.
1 reply 1 retweet 4 likes -
Replying to @BrendanEich @AdamRackis and
Native apps want better security than OS sandboxing + App Store "curation" (too much malware in the big stores, esp. Google Play). Let the Web shine where it does, take away "need" for bogo-native apps by working together to fast-follow OS APIs that fit the Web's security model.
1 reply 0 retweets 4 likes -
Replying to @BrendanEich @AdamRackis and
I'll end on friendly note: Google's work on PWAs has been very helpful to take away bogo-native-app need (see the Twitter example). More like that please, less defensive rear-guard arguing about past miscalculations. Smaller is better where possible. Follow the CR/stage 3 rules!
1 reply 2 retweets 4 likes -
Replying to @BrendanEich @AdamRackis and
All of that work was done the same way: commitment to leadership, based on competitive analysis, working with partners to validate the model and features. Can't get that sort of progress without approaches that leave space for leadership.
2 replies 0 retweets 2 likes
(citation: served as co-TL for the team that built PWAs + subsequent improvements)
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.