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 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dfabu @graynorton and

      Reuse in big teams. WCs done well end the "does X component work in my app?" slog. Also, all the React use claims I've seen have big asterisks; do you have pointers to better data?

      2 replies 0 retweets 5 likes
    2. Gray Norton‏ @graynorton 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @dfabu and

      • As Alex said, interop is a huge win for large orgs with multiple teams & disparate stacks • Yes, React ecosystem is huge today, but the entire web ecosystem benefits if more vendors (like Ionic) ship components that work well with *every* framework

      1 reply 0 retweets 9 likes
    3. Gray Norton‏ @graynorton 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graynorton @slightlylate and

      • Preact is great; if it's meeting all your needs, no reason for you to switch • lit-html and LitElement will get smaller when Template Instantiation lands in the platform • SSR is possible with web components, just not as far along – check Ionic's recent work here

      2 replies 0 retweets 9 likes
    4. Dan Fabulich‏ @dfabu 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graynorton @slightlylate and

      If there's no reason to switch from Preact, then why should anyone standardize on WCs as opposed to standardizing on Preact?

      2 replies 0 retweets 0 likes
    5. Dan Fabulich‏ @dfabu 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dfabu @graynorton and

      Overall, if the answer to "why switch from Preact to WCs" is "no reason at all; in fact, SSR gets worse" then we should try to standardize Preact/React components in userland and turn the result into a "std" layered API.

      1 reply 0 retweets 0 likes
    6. Gray Norton‏ @graynorton 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dfabu @slightlylate and

      The fact that there's no reason for you (or any given individual dev) to switch to WCs today doesn't mean that there's not value in the ecosystem as a whole shifting to adopt a platform-native component model eventually, as the standards evolve.

      1 reply 1 retweet 5 likes
    7. Gray Norton‏ @graynorton 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graynorton @dfabu and

      In practice, the web ecosystem will never standardize on any particular userland solution, and shouldn't. Layered APIs don't really change this equation; they're just a new way for the platform to ship features, with a "pay-for-what-you-use" consumption model.

      1 reply 0 retweets 4 likes
    8. Dan Fabulich‏ @dfabu 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graynorton @slightlylate and

      The problem is that we won't standardize on custom elements with shadow DOM, either. Thanks to slot SSR rehydration issues, userland SSR solutions are faster to paint than the "standard" and just as fast to TTI.

      1 reply 0 retweets 0 likes
    9. Gray Norton‏ @graynorton 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dfabu @slightlylate and

      It's not clear that the rehydration challenges with Shadow DOM are unsolvable. In the worst case (tho I doubt it will come to this), it will be back to the drawing board. Userland solutions are a good measuring stick for platform features, which inevitably have a longer arc.

      2 replies 0 retweets 2 likes
    10. Dan Fabulich‏ @dfabu 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graynorton @slightlylate and

      Narrator: It did, eventually, come to this. In a few years, we'll take a deep breath and add a virtual DOM "std" layered API, tightly integrated with DOM Display Locking. Everybody will wonder what took Google so long to come around.

      3 replies 0 retweets 0 likes
      Alex Russell‏ @slightlylate 12 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dfabu @graynorton and

      It's unclear, in this story, who you think was driving all the other rounds of progress, not to mention LAPIs and Display Locking 🤔

      1:09 PM - 12 Apr 2019
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Dan Fabulich‏ @dfabu 12 Apr 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @graynorton and

          Google! Including you, specifically! (Thanks, I really mean it!) But I still think we'll look back on today's iteration of WCs as a big distraction from the right thing.

          1 reply 0 retweets 0 likes
        3. Alex Russell‏ @slightlylate 12 Apr 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @dfabu @graynorton and

          We've certainly paid a large opportunity cost in the V0 -> V1 transition and, if I had it to do over, we'd have been focused on these problems instead of a migration to a slightly-but-not-enough-better starting point.

          0 replies 0 retweets 3 likes
        4. End of conversation

      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