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
mathias's profile
Mathias Bynens
Mathias Bynens
Mathias Bynens
Verified account
@mathias

Tweets

Mathias BynensVerified account

@mathias

I work on @ChromeDevTools & @v8js at Google and on ECMAScript through TC39. ♥ JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.

Munich, Germany
mths.be
Joined January 2007

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. Josh Burgess  🤔‏ @_joshburgess 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      A hill I will die on: There is no good reason to use `async/await` in JS/TS/Flow. - Specialized to thenables, not overloadable due to wrapping vals in promises - Tries to mask declarative async code as procedural sync code - No perf benefits vs 3rd party Promise implementations

      16 replies 8 retweets 65 likes
    2. angelo  🦊‏ @AngeloGulina 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @_joshburgess

      angelo  🦊 Retweeted Mathias Bynens

      Some time ago there was this: https://twitter.com/mathias/status/1062000234203496449?s=21 … True? Not true?

      angelo  🦊 added,

      Mathias BynensVerified account @mathias
      🔥 JavaScript performance advice: 1. prefer `async`/`await` over hand-written promise code
 2. prefer native promises over userland implementations https://v8.dev/blog/fast-async  https://twitter.com/v8js/status/1062000102909169670 …
      2 replies 0 retweets 1 like
    3. Josh Burgess  🤔‏ @_joshburgess 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @AngeloGulina

      I've seen people talk about how V8 optimizes it, and I, admittedly, don't know much about that, but when I last checked I saw that Promise libs like Bluebird & Creed, and other async libraries, like Most (streams) are significantly faster than native promises. Wasn't even close.

      2 replies 0 retweets 2 likes
    4. Martin Valdes de Leon‏ @mvaldesdeleon 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @_joshburgess @AngeloGulina

      The gist of it is that every time you use `then` a new Promise object is created, even if it's in a `then` chain where that particular Promise itself is never assigned to anything. When you use async/await, V8 is able to optimize these "intermediate" Promise objects away.

      1 reply 2 retweets 6 likes
    5. Josh Burgess  🤔‏ @_joshburgess 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mvaldesdeleon @AngeloGulina

      Does that really matter in practice though? I mean, if you start off with a library that's already much faster, like Bluebird or Creed, or skip promises altogether in favor of a fast streams library, does that async/await optimization make any meaningful difference?

      2 replies 0 retweets 1 like
    6. Mathias Bynens‏Verified account @mathias 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @_joshburgess @mvaldesdeleon @AngeloGulina

      The real-world benchmarks in the blog post seem to indicate that yes, this does indeed have a significant impact. Please read the blog post. +@MayaLekova @bmeurer

      2 replies 0 retweets 5 likes
    7. Martin Valdes de Leon‏ @mvaldesdeleon 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mathias @_joshburgess and

      The real-world benchmarks from the post show a ~50ms gain when switching from Promises to async/await. So, if you're looking to shed that last few ms off your request, then sure. But in most cases I've found in the real world, there are many other areas you'd optimize first.

      1 reply 0 retweets 1 like
      Mathias Bynens‏Verified account @mathias 15 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mvaldesdeleon @_joshburgess and

      That’s the thing — I wouldn’t consider async/await an optimization, but rather a substantial readability improvement. It’s a nice extra that the perf is now on par or better than vanilla promises. In general, we should all focus on writing readable, idiomatic, modern JS.

      5:11 AM - 15 Jan 2019
      • 1 Retweet
      • 3 Likes
      • Tarik Kyler Johnson Amir Mikhak Brian Scott
      3 replies 1 retweet 3 likes
        1. New conversation
        2. Josh Burgess  🤔‏ @_joshburgess 15 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @mvaldesdeleon and

          A substantial readability improvement according to who though? That's assuming that everyone prefers reading/writing procedural code over declarative code... which obviously isn't true if you look at all the people who use libraries like RxJS, etc.

          1 reply 1 retweet 1 like
        3. Martin Valdes de Leon‏ @mvaldesdeleon 15 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @_joshburgess @mathias and

          One issue I found with both Promise, Task and such, is when you need to keep multiple intermediate values in scope, and not just the last result. In Haskell, you'd use do-notation to avoid nesting the lambdas, and that is pretty much what you get when you use async/await.

          1 reply 0 retweets 1 like
        4. 1 more reply
        1. New conversation
        2. angelo  🦊‏ @AngeloGulina 15 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @mvaldesdeleon and

          On the ergonomic of it I think the opinions are various then 😄 I find piping better for brain to process and having to use try/catch really reduces readability

          1 reply 0 retweets 1 like
        3. Amir Mikhak‏ @feanorm 15 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @AngeloGulina @mathias and

          +1 I hate try-catch.

          0 replies 0 retweets 0 likes
        4. End of conversation
        1. Martin Valdes de Leon‏ @mvaldesdeleon 15 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @_joshburgess and

          But the thread was a discussion on why async/await might not required when working with other idiomatic alternatives in TypeScript, such as Task/TaskEither. It was not about vanilla promises in JS.

          0 replies 0 retweets 0 likes
          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