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.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • 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
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

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 Roach‏ @adambroach 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @fugueish @mik235 @davidben__

      Looks like Promise overhead is on the order of 25 ms for V8 nowadays: https://v8.dev/blog/fast-async  -- so... not much?

      2 replies 0 retweets 0 likes
    2. Jeffrey Yasskin‏ @jyasskin 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @adambroach @fugueish and

      "The above chart [which shows the 25ms you seem to be quoting] shows the doxbee benchmark, which measures performance of promise-heavy code." That's not just one Promise resolution.

      1 reply 0 retweets 0 likes
    3. Adam Roach‏ @adambroach 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jyasskin @fugueish and

      Sure, and if you're only invoking a single promise, execution time is negligible. I presumed we were discussing real-world impacts, not angels-dancing-on-a-pinhead tweaks.

      1 reply 0 retweets 0 likes
    4. Jeffrey Yasskin‏ @jyasskin 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @adambroach @fugueish and

      Your phrasing made @fugueish come to the conclusion that "Promises aren’t even 60 FPS", which, reading you again more carefully, is I think the opposite of the conclusion that you wanted.

      0 replies 0 retweets 0 likes
    5. Patrick Walton‏ @pcwalton 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @fugueish @jyasskin and

      For what it’s worth, I think async crypto is not the right choice in JS, for the same reason why it’s not the right choice in any other language.

      1 reply 0 retweets 6 likes
    6. Patrick Walton‏ @pcwalton 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @fugueish @jyasskin and

      I guess a good rule of thumb is “if it blocks your CPU core, it’s not async”? That principle would make I/O and WebGL async but crypto (AES-NI) sync.

      1 reply 0 retweets 5 likes
    7. Jeffrey Yasskin‏ @jyasskin 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @fugueish and

      Blocking the CPU core doesn't mean it needs to block rendering, but when we give main-thread JS sync APIs, that's what folks do. I guess another point in the design space would be to make crypto worker-only?

      2 replies 0 retweets 1 like
      Patrick Walton‏ @pcwalton 31 Dec 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jyasskin @fugueish and

      OMT layout sure would be nice (if it’s web compatible) ;) Anyway, how slow are we talking about anyway? AES-NI is really fast.

      3:07 PM - 31 Dec 2018
      • 1 Like
      • Jeffrey Yasskin
      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