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. Rich Harris‏Verified account @Rich_Harris 23 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whatjustin @justinformentin @0ndras

      Do you mean you're putting SVGs inside CEs? Because yeah, of course that works — you can always put an <svg> inside an HTML element. But you can't put custom elements inside an <svg>

      2 replies 1 retweet 11 likes
    2. Justin‏ @whatjustin 23 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Rich_Harris @0ndras

      Oh gotcha, yeah.

      1 reply 0 retweets 3 likes
    3. Alex Russell‏ @slightlylate 23 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whatjustin @justinformentin and

      Insufficient extensibility is a problem for sure, and one we can address, bit it's hard to take it as an argument against expanded extensibility offered to date (unless you expect the platform to be frozen from this date onward).

      1 reply 0 retweets 3 likes
    4. Rich Harris‏Verified account @Rich_Harris 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @justinformentin @0ndras

      It's simpler than that: if I'm starting a new app today, I can either a) hope that my requirements don't evolve to include SVG components, or b) use tools and practices that don't rely on custom elements

      1 reply 1 retweet 11 likes
    5. Ben Delarre‏ @BenDelarre 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Rich_Harris @slightlylate and

      You could use today's tech and build your app. And if your needs expand use the tools you need then. Saying you can't use a new tech today because it doesn't solve all future problems is like saying you can't drive the nail because the hammer doesn't work for screws too!

      1 reply 0 retweets 2 likes
    6. pngwn‏ @evilpingwin 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BenDelarre @Rich_Harris and

      This is ludicrous. Start with WC and if you end up needing svg support rebuild it all?

      1 reply 0 retweets 6 likes
    7. Rich Harris‏Verified account @Rich_Harris 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @evilpingwin @BenDelarre and

      yeah, that's borderline professional negligence. you need to pick technologies that won't paint you into a corner

      1 reply 0 retweets 5 likes
    8. Ben Delarre‏ @BenDelarre 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Rich_Harris @evilpingwin and

      Miss the point much? WC do not lock you in at all. Because they are HTML and standards based anything that works with HTML works with WC. Use WCs where it makes sense. When you need more use the appropriate tool. It'll interop with WC because it has to if it supports HTML!

      3 replies 0 retweets 2 likes
    9. pngwn‏ @evilpingwin 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BenDelarre @Rich_Harris and

      What's the point though? There are tools that don't bring this level uncertainty, I'd rather go with one of them and get on with my life.

      1 reply 0 retweets 1 like
    10. Rich Harris‏Verified account @Rich_Harris 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @evilpingwin @BenDelarre and

      Exactly. No a11y caveats. No SSR caveats. No risk of global namespace conflicts. No SVG limitations. No restrictions around how I get styles into my app. Etc. I just don't need to waste brain cycles thinking about how I'm going to work around all these issues

      1 reply 0 retweets 4 likes
      Alex Russell‏ @slightlylate 24 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Rich_Harris @evilpingwin and

      Rather, you're only left with all the existing a11y caveats, style workarounds, and integration limitations (e.g. forms) of not participating in the system in a first class way.

      10:14 AM - 24 Nov 2019
      • 2 Likes
      • Caleb Williams Ben Delarre
      2 replies 0 retweets 2 likes
        1. Rich Harris‏Verified account @Rich_Harris 24 Nov 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @evilpingwin and

          What existing a11y caveats? If you're saying that WCs are somehow inherently superior a11y-wise to something like e.g. Reach UI, then you're spouting nonsense. And empirically, styling is simply *easier* when you don't have shadow DOM in the way, unless you're e.g. building LWC

          0 replies 0 retweets 3 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. Daniel Schildt‏ @autiomaa 24 Nov 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @Rich_Harris @evilpingwin

          The biggest difference is amount of time. For people who develop small applications frequently (or maintain larger), what matters most is the learning curve of a technology. Most tools solve problems with enough of time. Most people don't have enough time.

          0 replies 0 retweets 1 like
          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