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. David Benjamin‏ @davidben__ 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jaffathecake @jyasskin and

      Much of WebCrypto has no business being asynchronous. Promises and friends make sense for IO-bound operations, while crypto is CPU-bound. Most of it is also quite fast, to the point that the promise machinery costs more than the operation itself.

      2 replies 0 retweets 3 likes
    2. David Benjamin‏ @davidben__ 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @davidben__ @jaffathecake and

      If it's CPU-bound and slow, that probably also justifies promises + worker pool (RSA keygen definitely, maybe some other asymmetric operations), but the symmetric ops should have been synchronous.

      1 reply 0 retweets 1 like
    3. Alex Russell‏ @slightlylate 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @davidben__ @jaffathecake and

      I/O+bound isn't different to CPU-bound when responsiveness is at risk. Environments without threading rely on tasks deferring for responsiveness.

      2 replies 0 retweets 2 likes
    4. David Benjamin‏ @davidben__ 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @jaffathecake and

      Which is why I mentioned symmetric vs asymmetric operations. Computing a hash is not a responsiveness risk. We're talking operations where we look at avoiding malloc because it's on the radar at this scale.

      1 reply 0 retweets 3 likes
    5. Jeffrey Yasskin‏ @jyasskin 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @davidben__ @slightlylate and

      … the TAG should probably give some guidance about when a CPU-bound operation takes long enough to make it promise-based. e.g. Hashes and AES handle 1MB in about 1ms, which is probably fine to block the main thread, but we also just added img.decode() because images take longer.

      3 replies 0 retweets 2 likes
    6. David Benjamin‏ @davidben__ 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jyasskin @slightlylate and

      (Not sure yet how much I believe this claim) Perhaps CPU-bound alone justifies sync, but maybe not callable on UI thread. You won't do better than a background thread, be it app- or browser-owned. Former is more flexible and inherits existing DoS limits. Latter needs custom limit

      1 reply 0 retweets 1 like
    7. Alex Russell‏ @slightlylate 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @davidben__ @jyasskin and

      "UI thread" is the sort of assumption in system design that frequently defeats responsiveness (while improving throughput). Most engineers live in someone else's framework; also responsiveness is king on the client side.

      0 replies 0 retweets 2 likes
    8. Alex Russell‏ @slightlylate 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BRIAN_____ @davidben__ and

      I hear compilers are "a thing" these days.

      2 replies 0 retweets 4 likes
    9. Jake Archibald‏ @jaffathecake 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @BRIAN_____ and

      If equivalent WASM'd crypto methods are outperforming native ones, can we at least agree that's a problem worth solving?

      1 reply 0 retweets 3 likes
      Alex Russell‏ @slightlylate 28 Jul 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jaffathecake @BRIAN_____ and

      "outperforming" is multi-faceted

      11:48 PM - 28 Jul 2018
      • 3 Likes
      • Designeour Ryan Sleevi Mark Nottingham
      1 reply 0 retweets 3 likes
        1. New conversation
        2. Jake Archibald‏ @jaffathecake 29 Jul 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @BRIAN_____ and

          For this particular crypto case it'd be good to know specifics. What's the size and shape of the issue before and after WASM.

          1 reply 0 retweets 1 like
        3. Alex Russell‏ @slightlylate 29 Jul 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @jaffathecake @BRIAN_____ and

          WASM doesn't change anything other than that people who were C/C++ folks were sold a "minimal changes" bill of goods.

          1 reply 0 retweets 2 likes
        4. 5 more replies

      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