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. rossipedia‏ @rossipedia 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @threepointone @Rich_Harris and

      bundlephobia needs to add parse/execution time. download size is only part of the problem

      1 reply 0 retweets 2 likes
    2. rtorr 🅧‏ @richardiii 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rossipedia @threepointone and

      There is a lot of hidden cost to bundle size. Debugging, domain knowledge etc

      1 reply 0 retweets 2 likes
    3. rossipedia‏ @rossipedia 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @richardiii @threepointone and

      well, yeah... which is still only part of the problem. I wasn't trying to diminish its role, rather point out that parse/execution time are often overlooked and play as big a role in the end-user experience

      2 replies 0 retweets 4 likes
    4. Matthew Phillips‏ @matthewcp 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rossipedia @richardiii and

      Is there an easy way to get parse/execution time?

      1 reply 0 retweets 0 likes
    5. rossipedia‏ @rossipedia 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthewcp @richardiii and

      it's a bit complicated, as that depends quite a bit on what device it's running on. but a couple baselines numbers measured from popular devices would be helpful (iPhone, Galaxy, and possibly a lower end device as well)

      1 reply 0 retweets 0 likes
    6. Matthew Phillips‏ @matthewcp 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rossipedia @richardiii and

      Sorry, I was asking if you know of a way for a tool like bundlephobia to get this information (rather than rely on people to provide it for their own stuff)?

      1 reply 0 retweets 0 likes
    7. Rich Harris‏Verified account @Rich_Harris 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthewcp @rossipedia and

      I bet @slightlylate knows

      2 replies 1 retweet 0 likes
    8. Addy Osmani‏Verified account @addyosmani 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Rich_Harris @matthewcp and

      Fyi parse/compile is pretty fast in V8 in many cases now. It's download + execution time dominating. Parse/compile can be measured via Lighthouse or Chrome DevTools Protocol. Look for the "scriptParseCompile" group. There are however some quirks with this today cc @mathiaspic.twitter.com/bzWTRZNYUf

      3 replies 0 retweets 22 likes
    9. Mathias Bynens‏Verified account @mathias 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @addyosmani @Rich_Harris and

      Currently the only reliable way to get the main thread parse + compile cost is through chrome://tracing + RuntimeCallStats. Both Lighthouse and DevTools expose background thread time as well (which doesn’t matter, since it doesn’t block loading). We’re working to improve this!

      1 reply 0 retweets 7 likes
    10. Alex Russell‏ @slightlylate 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mathias @addyosmani and

      "doesn't block loading" is contingent. If you structure your app to depend on the script, it'll still "block" even of the work is on a different thread.

      1 reply 0 retweets 0 likes
      Mathias Bynens‏Verified account @mathias 8 Apr 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @addyosmani and

      True. With ScriptStreamingOnPreload (which we hope to ship in Chrome 75), this becomes less likely though. In many cases we complete parse + compile by the time the HTML parser sees the starting <script> tag, and we can just start executing right away. @leszekswirski

      12:02 PM - 8 Apr 2019
      • 3 Likes
      • Andy Davies Rich Harris Andrew Levine
      1 reply 0 retweets 3 likes
        1. New conversation
        2. Leszek Swirski‏ @leszekswirski 8 Apr 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @slightlylate and

          Yes, and even if it's not ready, that's (mostly) due to network rather than parse. It's valuable to expose and to analyse, but as "download time" rather than "parse time" so that devs have a better idea of what to optimise (e.g. use brotli, invest in CDNs, etc.)

          1 reply 0 retweets 1 like
        3. Yoav Weiss‏ @yoavweiss 8 Apr 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @leszekswirski @mathias and

          Moving parse and compile out of the equation is truly awesome. Still, slow executing scripts can be blocking if that's how you built your app

          1 reply 0 retweets 3 likes
        4. 1 more reply

      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