Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
slightlylate's profile
Alex Russell
Alex Russell
Alex Russell
@slightlylate

Tweets

Alex Russell

@slightlylate

Chrome Project 🐡 & Web Standards TL; Blink API OWNER Named PWAs w/ @phae; probably making her ☕ DMs open. Tweets my own; press@google.com for official comms.

San Francisco, The Internet
infrequently.org
Joined December 2010

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @plinss and

      To enable that ideal scenario, Blink invests massively in compat, tests, OT infra, process, etc. One concern now is that we've done a huge amount to get compat for existing features but are pulling away on investment levels for new work, endangering competitiveness.

      1 reply 0 retweets 1 like
    2. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @plinss and

      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.

      1 reply 0 retweets 1 like
    3. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    4. Rick Byers‏ @RickByers Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    5. Adam Rackis‏ @AdamRackis Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    6. BrendanEich‏Verified account @BrendanEich Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    7. BrendanEich‏Verified account @BrendanEich Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    8. BrendanEich‏Verified account @BrendanEich Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    9. BrendanEich‏Verified account @BrendanEich Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
    10. BrendanEich‏Verified account @BrendanEich Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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
      Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      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.

      11:31 AM - 26 Jan 2020
      • 2 Likes
      • Mike Sherov (he/him) 🚀 Chidozie Ndukaku
      2 replies 0 retweets 2 likes
        1. Alex Russell‏ @slightlylate Jan 26
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @BrendanEich and

          (citation: served as co-TL for the team that built PWAs + subsequent improvements)

          0 replies 0 retweets 0 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. New conversation
        2. BrendanEich‏Verified account @BrendanEich Jan 26
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @AdamRackis and

          You are on the back foot arguing both WC V0 was righteous even though unflagged early; but don't use it even though we can't remove it now. CR/stage-3 or bust.

          1 reply 0 retweets 3 likes
        3. Alex Russell‏ @slightlylate Jan 26
          • Report Tweet
          • Report NetzDG Violation
          Replying to @BrendanEich @AdamRackis and

          I did err there: V0 mistake was agreeing to incompatible V1 rather than scoped additions to remove warts. Mozilla and MSFT failing timely implementation post hostage taking Moz blog post showed the folly.

          1 reply 0 retweets 0 likes
        4. 1 more reply

      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.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info