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. Peter Linss‏ @plinss Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @mikesherov and

      And that is appreciated more than you realize, but it doesn’t equate to “we’re doing this well enough that there’s no need for competing engines with other approaches, needs, and viewpoints”.

      2 replies 0 retweets 2 likes
    2. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @plinss @mikesherov and

      Again, that's categorically not what happened here (because our process works to prevent it). Follow the links and look at the evidence: https://github.com/w3ctag/design-reviews/issues/308 … https://groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/irhrlr6n5YQ/LOS8xSGsBwAJ …https://groups.google.com/a/chromium.org/forum/m/#!topic/blink-dev/gL2EVBzO5og/discussion …

      1 reply 0 retweets 3 likes
    3. Peter Linss‏ @plinss Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @mikesherov and

      I wasn’t replying to the specific issue of constructible stylesheets but to your statement about “engine diversity absolutists”.

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

      I see. The statement was a request for a better argument than a blanket appeal to engine diversity as the highest good. We can both trivially imagine scenarios in which we achieve a multitude of engines but fail on most other dimensions, right?

      1 reply 0 retweets 1 like
    5. Peter Linss‏ @plinss Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @mikesherov and

      Of course. We can also imagine scenarios where we fall into another browser monoculture and fail to take the web in the best possible direction, right? As I said, there’s tension, that’s a *good* thing, even when it’s painful. It keeps us all honest and doing our best.

      1 reply 0 retweets 4 likes
    6. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @plinss @mikesherov and

      Now we're getting somewhere! Browser monocultures of yore happened pre-OSS. How does that change the calculus? Browser monoculture implies engine monoculture, but the inverse isn't strictly true, right?

      1 reply 0 retweets 2 likes
    7. Peter Linss‏ @plinss Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @mikesherov and

      You’re not seriously saying engine monoculture would be a good thing, are you? And FWIW, Gecko went open source in the 90s, prior to the monoculture desert. Having an open source engine isn’t enough to prevent that.

      1 reply 0 retweets 5 likes
    8. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @plinss @mikesherov and

      I'm not making claims that monoculture is good *or* bad. It presents risk, tho. In MSFTs example, big realised risk was disinvestment. On Gecko; wasn't NN/Mozilla's shipping engine until the 00s, right? I ran the nightlies, but it wasn't 1.0 until 2002, IIRC.

      2 replies 0 retweets 2 likes
    9. Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @plinss and

      So what is an ideal scenario? Imagine multiple engines all compatible about 99% of features all the time, exploring the frontier of new features separately, but safely, then quickly converging. Assuming such a scenario represents a competitive platform, that's pretty 👍

      2 replies 0 retweets 3 likes
    10. This Tweet is unavailable.
      Alex Russell‏ @slightlylate Jan 26
      • Report Tweet
      • Report NetzDG Violation
      Replying to @groby @plinss and

      That's still how W3C process works. But also, RFC interop was *never* a gate to shipping product in IETF land, and that's what some seem to be demanding.

      10:57 AM - 26 Jan 2020
      • 3 Likes
      • Domenic Denicola Justin Donnelly Mike Sherov (he/him) 🚀
      3 replies 0 retweets 3 likes
        1. New conversation
        2. Alex Russell‏ @slightlylate Jan 26
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @groby and

          The Blink Launch Process is conscious of this history and does not gate on formal standards phases, but takes a risk-based approach to interop.

          1 reply 0 retweets 0 likes
        3. Adam Rackis‏ @AdamRackis Jan 26
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @groby and

          As before, one has to wonder why you couldn’t just ship behind a flag, with a provided polyfill, *until* those two interoperable implementations existed. Ideally there’s a better answer than “we wanted it now and others weren’t moving fast enough.”

          0 replies 0 retweets 1 like
        4. End of conversation
      1. This Tweet is unavailable.
        1. Mike Sherov (he/him)  🚀‏ @mikesherov Jan 26
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @groby and

          IETF has "rough consensus and running code".

          0 replies 0 retweets 0 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      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