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. Tony “Abolish ICE” Arcieri  🦀‏ @bascule 23 May 2019
      • Report Tweet
      • Report NetzDG Violation

      Every time I see another poll about the @rustlang async/await syntax, I feel like it's missing the option "I just want async/await to be stable and will defer to the Rust Core team's best judgment about the syntax"

      5 replies 10 retweets 100 likes
      Show this thread
    2. mik‏ @mik235 23 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @bascule @rustlang

      mik Retweeted mik

      I don't currently do any Rust programming, but thread FWIW: https://twitter.com/mik235/status/1129246179835883520 … (async/await is a mistake)

      mik added,

      mik @mik235
      Everything in Javascript is async and runs in a single thread. Javascript has tried nearly all the models for dealing with that - unfortunately the best model (coroutines) is just too hard to bolt on.
      Show this thread
      2 replies 0 retweets 2 likes
    3. Chris Palmer‏ @fugueish 23 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mik235 @bascule @rustlang

      Promises/async/await seem like a total hack necessary for JavaScript only. Why would languages that don’t need (Rust, C++) it adopt it? What am I missing? It’s miserable in JS, too.

      4 replies 0 retweets 5 likes
    4. Patrick Walton‏ @pcwalton 23 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @fugueish @mik235 and

      Because it’s the fastest of all available options. Coroutines needs stacks and are therefore slower.

      4 replies 0 retweets 6 likes
    5. Chris Palmer‏ @fugueish 23 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @mik235 and

      I don’t see how that necessarily follows, but I’ll believe you

      1 reply 0 retweets 1 like
    6. Patrick Walton‏ @pcwalton 23 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @fugueish @mik235 and

      It’s mostly all about malloc perf. Async/await avoids allocations (alliteration!) BTW, the syscall cost of spawning a thread on Linux is a lot less than the cost of allocating the stack.

      3 replies 0 retweets 9 likes
    7. Brian Smith‏ @BRIAN_____ 23 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @fugueish and

      Put another way, basically in the Rust community "requires malloc" is synonymous with "DOA" unless the use of malloc is a temporary hack that people plan to eventually remove. Also legacy; async/await has a clear migration path from futures which is what people currently use.

      3 replies 0 retweets 0 likes
    8. Saoirse Shipwreckt‏ @withoutboats 24 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BRIAN_____ @pcwalton and

      None of this played any role whatsoever in the decision to move forward with futures and async/await. This is offensive and denigrating speculation

      1 reply 0 retweets 1 like
    9. Patrick Walton‏ @pcwalton 24 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @withoutboats @BRIAN_____ and

      (I didn’t read that comment as offensive, for what it’s worth. Just saying that avoiding unnecessary allocation is valued in Rust code, which seems pretty uncontroversial.)

      2 replies 0 retweets 2 likes
    10. Manish‏ @ManishEarth 24 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @withoutboats and

      Yes, but the reason async await are wanted is not to avoid allocation, it's to avoid context switching and for c10k. (The reason they're wanted over futures is that future chaining is annoying)

      1 reply 0 retweets 1 like
      Patrick Walton‏ @pcwalton 24 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth @withoutboats and

      Doesn’t context switching always happen anyway when you receive data on a socket?

      7:40 AM - 24 May 2019
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Manish‏ @ManishEarth 24 May 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @withoutboats and

          Maybe not comtext switching, sorry. But basically, c10k. c10k isn't primarily a complaint about malloc. Malloc is still part of all this, but a much smaller part

          2 replies 0 retweets 1 like
        3. Patrick Walton‏ @pcwalton 24 May 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @ManishEarth @withoutboats and

          What specifically is the problem with having 10k threads? I always heard memory/allocation was the main issue.

          1 reply 0 retweets 0 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