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. Adam Rackis‏ @AdamRackis Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RickByers @slightlylate and

      Adam Rackis Retweeted Rick Byers

      I'm glad you see the JS process as impressive! Why not set an example at Chrome to bring that sort of process to web standards? As the absolute dominant (borderline monopoly) browser, your example here could do a ton of good.https://twitter.com/RickByers/status/1221142523198001157 …

      Adam Rackis added,

      Rick Byers @RickByers
      Replying to @hrmny_ @slightlylate and 2 others
      FWIW this is how the web has ALWAYS evolved. Almost all APIs we use today we're shipped in the dominant engine prior to a standard being ratified (IE, Netscape, WebKit, now chromium). JavaScript language is a notable and impressive counter-example.
      2 replies 0 retweets 0 likes
    2. Alex Russell‏ @slightlylate Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @AdamRackis @RickByers and

      TC39 is deeply unhealthy and has been for a long time. We route around via DOM frequently. Holding it up as a positive example is a mistake.

      2 replies 0 retweets 3 likes
    3. Rick Byers‏ @RickByers Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @AdamRackis and

      I admit ignorance, never been to a TC39 meeting myself. All that I find impressive is that major new things like Wasm seem to come compatibly in all engines at about the same time, and (maybe?) in a reasonable timeframe? I can't imagine that happening elsewhere.

      3 replies 0 retweets 1 like
    4. Rick Byers‏ @RickByers Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RickByers @slightlylate and

      But I know I don't have the whole picture. The grass is always greener...

      2 replies 0 retweets 0 likes
    5. Reilly Grant → @reillyeon@toot.cafe‏ @reillyeon Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RickByers @slightlylate and

      I think in the end it depends on whether or not there is broad consensus not in the solution, but on the problem. Once people agree there is a problem worth solving it is easier to work together on a solution. Why put effort into something you don't really feel is valuable?

      1 reply 0 retweets 2 likes
    6. Rick Byers‏ @RickByers Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @reillyeon @slightlylate and

      Yeah, and often the best way to reach consensus on a problem is to trial or ship a solution for it in one engine and learn from real-world experience.

      1 reply 0 retweets 2 likes
    7. Adam Rackis‏ @AdamRackis Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RickByers @reillyeon and

      Honestly I'd be 1,000% ok with that. But now, if I'm reading the screenshots of the original post correctly, Chrome folks are saying the shipped thing can't be changed, because it would break the web, because it's shipped. *That's* the part where people get justifiably pissed.

      1 reply 0 retweets 1 like
    8. Adam Rackis‏ @AdamRackis Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @AdamRackis @RickByers and

      But that screenshot was of one person, and maybe doesn't speak for everyone in Chrome-land, so maybe the spec can just be broken and fixed. One would hope.

      2 replies 0 retweets 0 likes
    9. Reilly Grant → @reillyeon@toot.cafe‏ @reillyeon Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @AdamRackis @RickByers and

      I'm not familiar with this particular case. The way I read the last screenshot is that coming up with a plan to avoid breaking existing sites will definitely have to be part of the process of reaching compatibility.

      1 reply 0 retweets 2 likes
    10. Reilly Grant → @reillyeon@toot.cafe‏ @reillyeon Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @reillyeon @AdamRackis and

      In my opinion that's a burden the Chromium project needs to bear.

      2 replies 0 retweets 0 likes
      Alex Russell‏ @slightlylate Jan 25
      • Report Tweet
      • Report NetzDG Violation
      Replying to @reillyeon @AdamRackis and

      More to the point, it isn't clear a breaking change is even a good idea. Needless pain is only that. Now, back to the question: what compatible additions do folks want? We're open for business on that front.

      5:30 PM - 25 Jan 2020
      • 1 Like
      • Rick Byers
      0 replies 0 retweets 1 like

      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